|
From: Nicholas N. <nj...@ca...> - 2003-08-30 15:01:01
|
On Sat, 30 Aug 2003, Thomas Eschenbacher wrote: > I want to verify my KDE-3 application (kwave.sf.net) with valgrind, but > as soon as the main window appears the program exits and I see a bunch > of messages like these: > > ==18449== valgrind's libpthread.so: KLUDGED call to: sem_destroy > > What is going wrong, does that mean that there is a bug in my > application or is there a problem with valgrind and/or glibc/libpthread? Valgrind's libpthread implementation is incomplete; for some functions it pretends to implement them but just does a cheap imitation (a "kludge" -- maybe we should not use this word as it's meaning doesn't seem to be widely known), in the hope that this is enough; often it is. Unfortunately, it seems that for your application it's not enough. If you are keen, you could try hacking coregrind/vg_libpthread.c to implement sem_destroy() and any other "kludged" functions to a sufficient level for things to work. N |