|
From: <dou...@so...> - 2004-09-21 14:39:30
|
On 21/09/2004 14:55:50 valgrind-users-admin wrote: >In message ><OFC...@gr...phos> >douglas leeder <dou...@so...> wrote: > >> I can't get valgrind 2.2.0 memcheck to work on RedHat 8.0: >> >> Whatever program I try I always get the same response: >> >> $ valgrind --tool=memcheck <program> >> valgrind: Couldn't allocate address space for shadow memory >> valgrind: Are you using a kernel with a small user address space, >> valgrind: or do you have your virtual memory size limited? >^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > >So do you? No :-) # ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited file size (blocks, -f) unlimited max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 4091 virtual memory (kbytes, -v) unlimited The installation should be pretty much as it came straight off the CD. -- Douglas Leeder Software Engineer, Sophos |
|
From: <dou...@so...> - 2004-09-22 09:10:30
|
On 21/09/2004 16:06:53 Tom Hughes wrote:
>In message
><OFC...@gr...phos>
>douglas leeder <dou...@so...> wrote:
>
>> The installation should be pretty much as it came straight off the CD.
>
>How much physical memory and swap do you have? My guess is you are
>being limited by the overcommit algorithm in the kernel. If that is
>the case then the CVS version of valgrind may help.
>
We can't get access to CVS from our network - any chance of a development
snapshot?
On our Red Hat 8.0 test machine I've added 2 2G swap partitions to the
existing 512 Mb swap.
total: used: free: shared: buffers: cached:
Mem: 525746176 129859584 395886592 0 14532608 55644160
Swap: 4556677120 0 4556677120
And valgrind memcheck now works.
I think the error message should be changed to give a better idea of what
went wrong and how to fix it.
In the mean time perhaps an entry on the FAQ would help people:
"""
When I start valgrind 2.2.0 I get:
valgrind: Couldn't allocate address space for shadow memory
valgrind: Are you using a kernel with a small user address space,
valgrind: or do you have your virtual memory size limited?
What's going on?
Are you running on Red Hat 8.0? Do you have overcommit on/off [delete as
appropriate] switched on? Valgrind is [insert description of what it's
trying to do]
Try creating 2/4 [delete as appropriate] Gb of swap space.
"""
Thanks for your help.
--
Douglas Leeder
Software Engineer, Sophos
|
|
From: Nicholas N. <nj...@ca...> - 2004-09-25 15:45:53
|
On Wed, 22 Sep 2004 dou...@so... wrote: > I think the error message should be changed to give a better idea of what > went wrong and how to fix it. > > In the mean time perhaps an entry on the FAQ would help people: > > """ > When I start valgrind 2.2.0 I get: > valgrind: Couldn't allocate address space for shadow memory > valgrind: Are you using a kernel with a small user address space, > valgrind: or do you have your virtual memory size limited? > What's going on? > > Are you running on Red Hat 8.0? Do you have overcommit on/off [delete as > appropriate] switched on? Valgrind is [insert description of what it's > trying to do] > Try creating 2/4 [delete as appropriate] Gb of swap space. > """ Yes, the error message here is bad. It went into 2.2.0 at the last minute. It is better than the old one, which was just an assertion failure :) We did not even know that a too-small swap space caused it when the message was written, which is why it is not mentioned in the message. I will improve the message and look at improving the memory layout situation further when I get back from holiday, in a couple of weeks. N |
|
From: Julian S. <js...@ac...> - 2004-09-21 14:53:42
|
On Tuesday 21 September 2004 15:39, dou...@so... wrote: > On 21/09/2004 14:55:50 valgrind-users-admin wrote: > >In message > ><OFC...@gr...phos> > > > >douglas leeder <dou...@so...> wrote: > >> I can't get valgrind 2.2.0 memcheck to work on RedHat 8.0: > >> > >> Whatever program I try I always get the same response: > >> > >> $ valgrind --tool=memcheck <program> > >> valgrind: Couldn't allocate address space for shadow memory > >> valgrind: Are you using a kernel with a small user address space, > >> valgrind: or do you have your virtual memory size limited? > > > >^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > >So do you? > > No :-) > > # ulimit -a > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > file size (blocks, -f) unlimited > max locked memory (kbytes, -l) unlimited > max memory size (kbytes, -m) unlimited > open files (-n) 1024 > pipe size (512 bytes, -p) 8 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) 4091 > virtual memory (kbytes, -v) unlimited > > The installation should be pretty much as it came straight off the CD. This doesn't really answer Tom's question. On Red Hat 8 you need about 1.5GB swap available before memcheck 2.2.0 will start. I bet that's the problem. J |
|
From: Tom H. <th...@cy...> - 2004-09-21 15:41:40
|
In message <200...@ac...>
Julian Seward <js...@ac...> wrote:
>> The installation should be pretty much as it came straight off the CD.
>
> This doesn't really answer Tom's question.
Actually, that was pretty much what I was after...
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|