On 06/24/2011 04:25 PM, John Reiser wrote:
>> When the program runs by itself, all the malloc calls are successful.
>> However when I run it with valgrind's memcheck or massif tools (v
>> 3.6.0), a malloc call fails (which is trying to allocate around 6.4 Gb).
> Which Linux distribution, which Linu
I'm having a very difficult problem getting valgrind to execute a
program which allocates large amounts of memory (> 20 Gb)
When the program runs by itself, all the malloc calls are successful.
However when I run it with valgrind's memcheck or massif tools (v
3.6.0), a malloc call fails (which
07:15:12PM -0600, tom fogal wrote:
> Patrick Alken writes:
> > It is a 64 bit machine, and I reinstalled valgrind using
> > --enable-only64bit, and it did use the -m64 when compiling.
>
> I meant compiling the *app* 64bit. e.g. if you're running:
>
> valgrind
It is a 64 bit machine, and I reinstalled valgrind using
--enable-only64bit, and it did use the -m64 when compiling.
Unfortunately I get the same malloc failure as before.
Patrick
On Thu, May 14, 2009 at 03:03:37PM -0600, tom fogal wrote:
> patrick.al...@noaa.gov writes:
> > I am using valgrin
Hi,
I am using valgrind 3.4.1 to try to find a memory leak. My
program has an initial routine which allocates a lot of memory -
around 1 GB. When I run the program by itself it runs fine, however
when I run it under valgrind, one of the many malloc calls in
the initial routine fails.
Does anyon
