|
From: Jeremy F. <je...@go...> - 2003-12-23 01:05:44
|
On Mon, 2003-12-22 at 16:42, John Carter wrote: > Ok... > > 1) The reason why I'm using the bleeding edge Valgrind is I want to > use the new Full Virtualization stuff that allows non-statically > linked executables to be valgrinded. In particular ecos synthetic target > executables. Yup, makes sense. I was thinking that static support would be useful for this kind of thing. > 2) I have just tried Julian's suggested tweak to the linker script, it > required one or two more tweaks to get it to link. It now links > and run's outside of valgrind but under valgrind it says... > > valgrind -v --leak-check=yes ./MYPROG --io --nr --nw --exit > Executable is mapped outside of range 0x80d3000-0xbffff000 > failed to load /usr/local/lib/valgrind/stage2: Cannot allocate memory Ah, I think this we've chasing a red herring. The problem isn't your executable; it's the linker you used to build Valgrind. What does readelf -hls /usr/local/lib/valgrind/stage2 say? I'm guessing the Makefile in coregrind/x86 has used the wrong version of "ld" to make coregrind/x86/stage2.lds. J |