|
From: Patrick O. <pat...@in...> - 2006-03-07 12:33:38
|
On Tue, 2006-03-07 at 11:17 +0000, Tom Hughes wrote: > In message <114...@po...> > Patrick Ohly <pat...@in...> wrote: > > > I still think the handling of suid binaries called from inside > > programs running under valgrind control should be investigated > > further (#119404, listed as "possibly just close") and the > > failing suppression of uninitialized memory reads inside Linux > > pthreads has also irritated a few people on this list (#119446, > > not listed). > > Keeping with all the different builds of glibc that people use > and which all seem to manage to give different backtraces is a > major pain as far as the linuxthreads issue goes. There are suppressions which used to work fine. > Some of them are virtually impossible to suppress as I recall > as the write appears to come directly from the user program with > no sign of libpthread at all... That's exactly the problem here: why is the stack backtrace incomplete and doesn't list the write() as coming from inside libpthread? When I use --db-attach on such a write gdb correctly tells me that, but valgrind skips one level in the callstack. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. |