|
From: pkr <pan...@ya...> - 2004-08-05 10:43:18
|
Tom Hughes wrote:
> In message <411...@ya...>
> pan...@ya... wrote:
>
>
>>Linux(debug)# /usr/local/bin/valgrind -v --logfile=/var/dpvm_mem
>>/isan/bin/dpvm
>>Executable is mapped outside of range 0x80cd000-0x7ffff000
>>failed to load /usr/local/lib/valgrind/stage2: Cannot allocate memory
>
>
> Have you linked your program with an unusual load address?
>
Not that I know of. My system runs some standard linux processes
(httpd/xinetd) as well as some proprietary process.
What I see in /proc/<pid>/maps is that for all processes the maps start
from 08048000
ie.
Linux(debug)# cat /proc/1583/maps
08048000-0810b000 r-xp 00000000 00:000007 1451 /usr/sbin/httpd
0810b000-0810e000 rw-p 000c3000 00:000007 1451 /usr/sbin/httpd
Is it possible to make changes in valgrind or do the inevitable ?
ie change the load address in libc/ld-linux.so. (I remember this
discussed on some other mailing list...)
Some info that could be of help:
Linux(debug)# cat /proc/meminfo
total: used: free: shared: buffers: cached:
Mem: 1053306880 528330752 524976128 0 4698112 402055168
Swap: 0 0 0
MemTotal: 1028620 kB
MemFree: 512672 kB
MemShared: 0 kB
Buffers: 4588 kB
Cached: 392632 kB
SwapCached: 0 kB
Active: 12272 kB
Inactive: 446656 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 1028620 kB
LowFree: 512672 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Committed_AS: 412744 kB
VmallocTotal: 1007608 kB
VmallocUsed: 88144 kB
VmallocChunk: 919404 kB
Thanks,
Pankaj
> Unfortunately in order to use valgrind your program will need to have
> a load address in the range that valgrind reported. Normally linked
> programs should fit that criteria though.
>
> Tom
>
|