|
From: Tom H. <to...@co...> - 2006-03-07 12:42:49
|
In message <114...@po...>
Patrick Ohly <pat...@in...> wrote:
> On Tue, 2006-03-07 at 11:17 +0000, Tom Hughes wrote:
>
>> 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.
I was assuming it was a tail call from libpthread to write that
caused the stack frame to disappear.
Do you have DWARF debugging available for glibc and libpthread? or
have them built with frame pointers?
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|