Re: [Valgrind-users] Valgrind 2.2.0 memcheck failure on RedHat 8.0

[Julian S. <js...@ac...>]

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...>
> >
> >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