Re: [Valgrind-users] Valgrind malloc problem

[tom f. <tf...@al...>]

Patrick Alken <pat...@no...> 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 --whatever ./a.out

then you should get a.out via:

  gcc -blah -m64 -moreblah something.c

you can also check if the binary under test is 64bit with `file'.

-tom

> Patrick
> 
> On Thu, May 14, 2009 at 03:03:37PM -0600, tom fogal wrote:
> > Pat...@no... writes:
> > >   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 anyone know why this would happen? There is plenty of memory
> > > on the machine (64 GB).
> > 
> > Are you running in 32bit mode?  Make sure you're passing -m64 when
> > compiling with gcc.
> > 
> > -tom
> > 
> > ---------------------------------------------------------------------------
> ---
> > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> > production scanning environment may not be a perfect world - but thanks to
> > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i7
> 00
> > Series Scanner you'll get full speed at 300 dpi even with all image 
> > processing features enabled. http://p.sf.net/sfu/kodak-com
> > _______________________________________________
> > Valgrind-users mailing list
> > Val...@li...
> > https://lists.sourceforge.net/lists/listinfo/valgrind-users