I've just installed the very last valgrind version from yesterday, that
not just works with threaded applications but is additionally supposed to
debug threading functions.
From the valgrind homepage (http://developer.kde.org/~sewardj/):
Report misuses of the POSIX pthread API whenever they are detected.
Such errors behave like all other valgrind-reported errors (duplicates
are not shown, and specific errors can be suppressed).
valgrind reports this bug:
pthread_mutex_destroy: mutex is still in use
at 0x40523AB4: pthread_error (vg_libpthread.c:229)
by 0x405249B5: __pthread_mutex_destroy (vg_libpthread.c:825)
by 0x40625220: _IO_default_finish (in /lib/libc.so.6)
by 0x406233F0: _IO_file_finish@@GLIBC_2.1 (in /lib/libc.so.6)
by 0x4061ABED: _IO_fclose@@GLIBC_2.1 (in /lib/libc.so.6)
by 0x83A9452: destroy (in /home/m/fgfs/FlightGear/src/Main/fgfs)
by 0x83A9E36: gzclose (in /home/m/fgfs/FlightGear/src/Main/fgfs)
by 0x833008F: gzfilebuf::close(void) (zfstream.cxx:156)
by 0x805C6BF: fgInitFGRoot(int, char **) (/usr/include/g++/std/bastring.h:166)
by 0x805261E: mainLoop(int, char **) (main.cxx:1435)
Unfortunately, I am neither familiar with threading, nor do I have time to
debug this within the next three weeks. Is there a threading expert around?
m. :-)
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
