|
From: Nicholas N. <nj...@cs...> - 2005-03-09 15:04:25
|
On Wed, 9 Mar 2005, Christopher Travers wrote:
> I'm working on a project that recently building our executables with an
> indirect loader utility ("rtldi" http://www.bitwagon.com/rtldi/rtldi.html)
> instead of using ld-linux.so.2 directly. One of the unfortunate consequences
> of this is that valgrind no longer works with those executables (more
> specifically the program segfaults).
>
> I'm wondering if anyone has used valgrind with rtldi and if so, what sort of
> tweaking was required. The only interesting output I get is an invalid read,
> and the segfault. However, the same program works in valgrind without the
> rtldi loader, and runs fine with the rtldi loader outside of valgrind... any
> thoughts would be appreciated...
>
> ==31395== Invalid read of size 1
> ==31395== at 0x1B8E414B: (within /projects/images/bin/rtldi)
> ==31395== by 0x1B8E464F: (within /projects/images/bin/rtldi)
> ==31395== by 0x1B8E478B: (within /projects/images/bin/rtldi)
> ==31395== by 0x1B8E4C6C: (within /projects/images/bin/rtldi)
> ==31395== Address 0x114CC is not stack'd, malloc'd or (recently) free'd
I can't give you any specific advice about rtldi, but if you recompile it
with debugging info (-g) you'll get much more informative stack traces,
which may help identify the problem.
N
|