|
From: Nicholas N. <nj...@cs...> - 2005-03-22 14:35:14
|
On Tue, 22 Mar 2005 oli...@on... wrote: > Since the pthread emulation is gone I get a lot of those warnings: > > ==32250== Syscall param write(buf) points to uninitialised byte(s) > ==32250== at 0x1B9178CB: write (in /lib/i686/libpthread-0.10.so) > ==32250== by 0x80AF033: CCalThread::CCalThread(void* (*)(void*), > void*) (/cal/dev/source/libs/libcalbase/thread/ccalthread.h:23) That looks familiar, I've seen similar ones in pthreaded programs. > ==32250== 8160 bytes in 1 blocks are definitely lost in loss record 13 > of 14 > ==32250== at 0x1B901538: malloc (vg_replace_malloc.c:130) > ==32250== by 0x1B9134DE: __pthread_initialize_manager (in > /lib/i686/libpthread-0.10.so) > ==32250== by 0x1B913A4B: pthread_create@@GLIBC_2.1 (in > /lib/i686/libpthread-0.10.so) > ==32250== by 0x80AF033: CCalThread::CCalThread(void* (*)(void*), > void*) (/cal/dev/source/libs/libcalbase/thread/ccalthread.h:23) > > I just don't unterstand it, because all thread are being exited > successfully and pthread_exit is always called. I thought it might have > something to do with the join state, but they aren't even joinable. > It's the same code as shown above and adding a pthread_detach there > didn't help either. It's likely a bug in the pthreads library. > Maybe someone out there know how to fix this warnings...or are those > supression candidates? I believe so, for both of them. N |