|
From: I K <add...@ho...> - 2004-08-18 07:17:00
|
Fellow Valgrinders, I just installed Valgrind and tried to debug my program. The problem is that when I type, for example, " valgrind --tool=addrcheck -v ./hello " , I receive this : valgrind: vg_main.c:553 (layout_remaining_space): Assertion `(void*)-1 != vres' failed. I am sorry if this sounds dump. It's just my first day working with Valgrind and I didn't find any reference to this problem in Valgrind's documentation. I would really appreciate your help. Iyad _________________________________________________________________ Is your PC infected? Get a FREE online computer virus scan from McAfee® Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 |
|
From: Nicholas N. <nj...@ca...> - 2004-08-18 08:49:33
|
On Wed, 18 Aug 2004, I K wrote: > I just installed Valgrind and tried to debug my program. The problem is that > when I type, for example, " valgrind --tool=addrcheck -v ./hello " , I > receive this : > > valgrind: vg_main.c:553 (layout_remaining_space): Assertion `(void*)-1 != > vres' failed. > > I am sorry if this sounds dump. It's just my first day working with Valgrind > and I didn't find any reference to this problem in Valgrind's documentation. It's not a dumb question. Normally x86/Linux machines are setup with a 3G/1G user/kernel split of the address space. Do you know if your box has a different split, eg. 2G/2G? Can you post the output of 'cat /proc/self/maps' ? Also, can you try 'valgrind --tool=none ./hello' to see if that works? Thanks. N |
|
From: Tom H. <th...@cy...> - 2004-08-18 09:02:06
|
In message <BAY...@ho...>
I. K. <add...@ho...> wrote:
> I just installed Valgrind and tried to debug my program. The problem
> is that when I type, for example, " valgrind --tool=addrcheck -v
> ./hello " , I receive this :
Please include the version number when reporting a problem - it makes
like much easier.
> valgrind: vg_main.c:553 (layout_remaining_space): Assertion `(void*)-1
> != vres' failed.
This means that your system refused to allocate the shadow memory
space. What distribution and kernel are you using - this sort of
thing has been seen with some RedHat kernels but upgrading to the
latest kernel for that release usually solves it. In fact rebooting
often seems to solve it.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|