|
From: Paul S. <ps...@no...> - 2005-03-26 13:26:25
|
%% Jeremy Fitzhardinge <je...@go...> writes: jf> I also build Valgrind in a cross environment; that should be OK. Yep, I just wanted to give some background since the error seemed to be in the runtime environment. We actually had a version of Valgrind 2.0.0 kinda-sorta-semi-working in an environment similar to this one. >> ==975== >> ==975== Process terminating with default action of signal 11 (SIGSEGV): dumping core >> ==975== Access not within mapped region at address 0xBF7FFC61 >> ==975== at 0x1B8E4A50: (within /lib/ld-2.3.2.so) jf> This address (0xBF7FFC61) is within Valgrind's address space, so jf> it looks like a Valgrind-internal error, though for some reason it jf> didn't trigger the normal internal-error printing code. Do I need to build valgrind with any flags to get better reporting? >> Anyone have any ideas, or pointers for me to move forward solving this >> problem? jf> We've never tested running inside UML, so that's one unknown. jf> Does it happen with other tools (try --tool=none)? No, all the other tools work, including addrcheck. Except helgrind; that says: # /opt/tools/bin/valgrind --tool=helgrind /bin/echo hi Can't open tool "helgrind": /opt/tools/lib/valgrind/vgskin_helgrind.so: undefined symbol: vgPlain_get_current_or_recent_tid valgrind: couldn't load tool but that seems to be something different. -- ------------------------------------------------------------------------------- Paul D. Smith <ps...@no...> HASMAT: HA Software Mthds & Tools "Please remain calm...I may be mad, but I am a professional." --Mad Scientist ------------------------------------------------------------------------------- These are my opinions---Nortel Networks takes no responsibility for them. |