|
From: Edwin M. <em...@ho...> - 2004-04-05 10:25:44
|
Hi, Currently is am facing a problem concerning the use of a semaphore. valgrind: vg_libpthread.c:2581 (sem_wait): Assertion `res == 0' failed. ==5262== Please report this bug at: valgrind.kde.org ==5262== TRANSLATE: 0x3C33E610 redirected to 0x3C13CD28 ==5262== ==5262== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 24 from 2) ==5262== ==5262== 1 errors in context 1 of 1: ==5262== Thread 29: ==5262== pthread_cond_wait/timedwait: mutex is unlocked or is locked but not owned by thread ==5262== at 0x3C13AD26: pthread_cond_wait (vg_libpthread.c:1316) ==5262== by 0x3C13DD2B: sem_wait (vg_libpthread.c:2579) ==5262== by 0x80EBA13: cGosyCountSemImpl::Wait(unsigned) (gosy_countsem.cpp:113) ==5262== by 0x80EB781: cGosyCountSem::Wait(unsigned) (gosy_countsem.cpp:32) --5262-- --5262-- supp: 23 Ugly strchr error in /lib/ld-2.3.2.so --5262-- supp: 1 pthread_mutex_unlock/_IO_funlockfile ==5262== ==5262== IN SUMMARY: 1 errors from 1 contexts (suppressed: 24 from 2) My configuration: Suse 9.0 kernel 2.4.21-99 glibc 2.3.2 valgrind 2.1.1 In the faq i read: ** A10. Thread support on glibc 2.3.2+ with NPTL is not as ** good as on older LinuxThreads-based systems. We have Is this my problem? What is NPTL? Any workarounds for having valgrind up-and-running? Edwin P.S. getpid() always returns the same id, no matter which thread is actually executing this call. Known issue? _________________________________________________________________ Talk with your online friends with MSN Messenger http://messenger.msn.nl/ |