RE: [Valgrind-users] Failing to start valgrind

[<ale...@ex...>]

Here it is:

% cat /proc/self/maps
08048000-0804a000 r-xp 00000000 08:02 210862     /bin/cat
0804a000-0804b000 rw-p 00002000 08:02 210862     /bin/cat
0804b000-0804c000 rwxp 00000000 00:00 0
15556000-1556a000 r-xp 00000000 08:02 323984     /lib/ld-2.3.2.so
1556a000-1556b000 rw-p 00014000 08:02 323984     /lib/ld-2.3.2.so
1556b000-1569c000 r-xp 00000000 08:02 323939     /lib/libc-2.3.2.so
1569c000-156a1000 rw-p 00130000 08:02 323939     /lib/libc-2.3.2.so
156a1000-156a4000 rw-p 00000000 00:00 0
3fffe000-40000000 rwxp fffff000 00:00 0

Alex 

-----Original Message-----
From: Nicholas Nethercote [mailto:nj...@cs...] 
Sent: Friday, May 27, 2005 9:28 PM
To: Ivershen, Alex
Cc: val...@li...
Subject: Re: [Valgrind-users] Failing to start valgrind

On Fri, 27 May 2005 ale...@ex... wrote:

> We've been using Valgrind here for quite a while, and I have never 
> seen this problem ... I have built Valgrind on a Linux box and 
> whenever I try to run it, I get this:
>
> %valgrind --version
> Executable range 0xb0000000-0xb01eafc0 is outside the acceptable range

> 0x80d4000-0x3ffff000
> valgrind: failed to load /usr/lib/valgrind/stage2: Cannot allocate 
> memory

What's the output of 'cat /proc/self/maps' ?

N