|
From: Gergely B. <ger...@me...> - 2004-11-16 12:50:31
|
Hi, valgrind tells me: $ valgrind --tool=memcheck [...] 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 should I do? - Gergely |
|
From: Nicholas N. <nj...@ca...> - 2004-11-17 17:53:44
|
On Tue, 16 Nov 2004, Gergely Buday wrote: > valgrind tells me: > > $ valgrind --tool=memcheck [...] > 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 should I do? If you are using RedHat 8.0, if you increase your swap size to about 2GB it may work. Otherwise, if you have a ulimit set for virtual memory, remove the limit. Otherwise, if you have a kernel with an unusual user/kernel split (ie. not the usual 3:1GB) you could try Valgrind from CVS, which handles that better on recent systems. Otherwise, I'm out of ideas. N |
|
From: Gergely B. <ger...@me...> - 2004-11-18 10:47:52
|
Nicholas Nethercote wrote: > On Tue, 16 Nov 2004, Gergely Buday wrote: > >> valgrind tells me: >> >> $ valgrind --tool=memcheck [...] >> 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 should I do? > > > If you are using RedHat 8.0, if you increase your swap size to about > 2GB it may work. Otherwise, if you have a ulimit set for virtual > memory, remove the limit. Otherwise, if you have a kernel with an > unusual user/kernel split (ie. not the usual 3:1GB) you could try > Valgrind from CVS, which handles that better on recent systems. > Otherwise, I'm out of ideas. Thanks, I've added 1G extra swap (up to 2G) on my Red Hat 7.3, and it worked. - Gergely |