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: > [email protected] 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 i700 > 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/valgrind-users ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
