|
From: Paul S. <ps...@no...> - 2005-03-28 23:28:24
|
%% Jeremy Fitzhardinge <je...@go...> writes: >> ==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. Hi all; I did some more poking today. First thing I discovered was that if I run the UML instance on the same version of system as it was built on (both compiled the UML kernel and ran it on Red Hat 8.0), then valgrind worked OK for most apps (but see a followup message for a different problem). If I run the UML instance on a different version of system (UML kernel built on redhat 8.0, but running it on Red Hat Enterprise Linux 3) then I see this error from valgrind. The bizarre part is that other than this the system works the same on both. And, as I mentioned in my followup email, only the memcheck tool shows this problem: the others, including addrcheck, are fine. I'm going to check with the UML folks to see what they think about this, but is there some "deeper magic" in terms of chumminess with the kernel that memcheck might assume, that the other tools don't, for example? -- ------------------------------------------------------------------------------- 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. |