|
From: Brian_Howell@PlayStation.Sony.Com - 2006-02-09 20:33:29
|
Had this problem with Valgrind on Fedora last year. After much search=
finally found what I needed to do and
had to recompile Valgrind.
I am now getting the same problem on Gentoo and now I am getting upset.=
[exec] sampleGameLobbyEPTest: no process killed
[exec] Result: 1
[exec] valgrind: no process killed
[exec] Result: 1
[exec] Executable range 0xb0000000-0xb080e7b0 is outside the
[exec] acceptable range 0x80d6000-0xaffff000
[exec] valgrind: failed to load /usr/lib/valgrind/stage2: Cannot
allocate memory
[exec] Result: 1
I can't remember where I put my workaround (involved recompilation an=
d
memory adjustment, yuck) and it seems like several people in mailing l=
ists
are having problem starting Valgrind on linux, especially Gentoo.
I don't want spend hours looking for the memory range so will some one
please help me to remember the workaround.
I am using 3.0.1-r1 Valgrind on Gentoo.
Here is just one of SEVERAL complaints file in Valgrind-users on this
issue, if there is not a bug there should be.
This email to the users list is similar to mine so don't need to file
another one myself. Only problem is that this one does not tell
KICKSTART_BASE to try.
Valgrind should be compiled with something Gentoo can deal with or why=
BOTHER putting it in the emerge tool if you have to do workaround.
I need a SIMPLE workaround that does not involve recompiling in the fut=
ure.
This is the second linux distrubution
I have used and second machine that I have used that showed this annoyi=
ng
problem.
FIX IT IN THE FUTURE, PLEASE!!!!!!!!!!!!!!!!!!!
Email Archive: valgrind-users (read-only) Search
=
From: Tom Hughes <thh@cy...> =
Re: Cannot start Valgrind =
2005-01-28 06:21 =
=
In message <000801c50446$16459d50$152ca8c0@nd> =
Ilkka Huotari <ihu...@cc...> wrote: =
=
> I"m using Gentoo Linux 2.4. I installed Valgrind yesterday, first w=
ith
> emerge tool, then compiling manually from the sources. =
> =
> With either way, whenever I try to run it, I get this: =
> =
> # valgrind =
> Executable range 0xb0000000-0xb01f4b40 is outside the =
> acceptable range 0x80d0000-0x7ffff000 =
> valgrind: failed to load /usr/lib/valgrind/stage2: Cannot allocate =
memory =
> =
> What might be wrong? =
=
It looks likes your valgrind is build for a 3:1 user:kernel memory =
split but your system has a 2:2 split so stage2 can"t be loaded as =
the address it was built for is up in kernel space. =
=
You can rebuild valgrind with KICKSTART_BASE changed to a lower =
address but with only 2Gb of address space you may have problems =
running large programs under valgrind. =
=
Do you know why Gentoo is using a 2:2 split? Most systems these seem =
to be moving to a 4:0 split if anything. =
=
Tom =
=
-- =
Tom Hughes (thh@cy...) =
Software Engineer, Cyberscience Corporation =
http://www.cyberscience.com/ =
=
=
=
Thread View
=
Thread Author Date =
=
Re: Cannot start Valgrind Tom Hughes <thh@cy...> 2005-01-28 06:21 =
=
=
=
|