Re: [Valgrind-developers] Switching PT_INTERP (helps Debian unstable)

[Julian S. <js...@ac...>]

> With the latest libc version, no symbol information shows up at all:
>
>  Conditional jump or move depends on uninitialised value(s)
>     at 0x1B8ECB13: (within /lib/ld-2.3.5.so)
>     by 0x1B8E631C: (within /lib/ld-2.3.5.so)
>     by 0x1B8F2BDD: (within /lib/ld-2.3.5.so)
>     by 0x1B8E7675: (within /lib/ld-2.3.5.so)
>     by 0x1B8E47C6: (within /lib/ld-2.3.5.so)

The same thing (or similar) happened in the release version of SuSE
9.3.  Shortly thereafter SuSE put a non-stripped version on their
online update and that made the problem go away, and they seem
to have stayed with that in SuSE 10.0 as Josef observes.  Which is
excellent.

I see what the patch is for and it looks plausible.  However to me
it is fixing the symptom -- the fundamental problem is that the
glibc packagers insist on removing ever more debugging info.

> By the way, are any of the Debian valgrind maintainers regular readers
> of this list? If not, I'll forward this information to the BTS.

Please hassle the Debian glibc maintainers.  Point out that they can't
expect to strip off all vestiges of debug info and still have a debuggable
system.  At least leave the symbols on.  /lib/ld-2.3.5.so is only on the
order of 110k even with symbols on, so there's really very little to
be gained from stripping it anyway.


J