|
From: Patrick O. <Pat...@gm...> - 2006-01-09 12:44:08
|
On Sat, 2006-01-07 at 19:03 -0800, John Reiser wrote: > > There isn't really a problem. LinuxThreads does this: [...] > > So, you can safely write a suppression for this error. There are already suppressions for this in valgrind's default glibc-2.2.supp which were good enough to suppress all errors in a program using LinuxThreads on RH AS2.1. However, since at least valgrind 3.0 they no longer work because of new stack backtraces like this one here (from Ron's report): ==17229== Syscall param write(buf) points to uninitialised byte(s) ==17229== at 0x4031A3B: write (in /lib/libpthread-0.10.so) ==17229== by 0x80484D4: main (main.c:13) ==17229== Address 0xBEFFF9AC is on thread 1's stack I had already reported this as http://bugs.kde.org/show_bug.cgi?id=119446 Bye, Patrick -- Telefonieren Sie schon oder sparen Sie noch? NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie |