|
From: Josef W. <Jos...@gm...> - 2005-08-26 17:47:09
|
On Friday 26 August 2005 05:23, Nicholas Nethercote wrote: > On Thu, 25 Aug 2005, Ashley Pittman wrote: > > This is key, it turns out I've been fooled by the RHEL4 > > prelinking/address space randomisation code again. Although the > > library's are the "same" to the extent that they come from the same rpm > > and the rpm passes a verify test the installed ones have been noodled in > > some way (not simply stripped). > > [...] > > My best guess is that in the prelinked library the "real" static symbols > > are being used where as in the non prelinked library the relocation > > table is being used and without having a handle on the relocation table > > valgrind isn't able to correlate the address with the source file. This > > isn't really my area of expertise though. > > So it sounds like this isn't really a problem with Valgrind, but an issue > with the environment? I do not think so. The prelinker of course does not change the debug information. Valgrind probably should take some additional address offset into account, which seems to be set to zero in the usual case without prelinking, so VG is working in the normal case. Is gdb able to show source lines with your prelinked library? Josef > > Nick > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |