Bug 115643 - valgrind cannot allocate memory
Summary: valgrind cannot allocate memory
Status: RESOLVED FIXED
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (show other bugs)
Version: 3.0.1
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-03 23:32 UTC by Walter Shands
Modified: 2005-11-16 17:38 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
NAS binary and source and output (18.23 KB, application/x-zip-compressed)
2005-11-03 23:33 UTC, Walter Shands 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Walter Shands 2005-11-03 23:32:16 UTC 
When trying to run NAS serial benchmark under valgrind, the message:

Executable range 0x400000-0x60502a20 is outside the
acceptable range (nil)-0x34a00000
valgrind: do_exec(./is.C) failed: Cannot allocate memory

is printed and execution ends.

The benchmark was compiled with f77 with -O option and an x86-64 target.
The OS is: SLES 9 (x86_64) - Kernel \r (\l)
Linux vtunep4ptl 2.6.5-7.139-smp #1 SMP Fri Jan 14 15:41:33 UTC 2005 x86-64 
x86-64 x86-64 GNU/Linux

Benchmark available at http://www.nas.nasa.gov/Software/NPB/
Comment 1 Tom Hughes 2005-11-03 23:33:28 UTC 
Please try this withthe current SVN code - the address space manager rewrite should have fixed it.
Comment 2 Walter Shands 2005-11-03 23:33:34 UTC 
Created attachment 13268 [details]
NAS binary and source and output
Comment 3 Walter Shands 2005-11-03 23:35:30 UTC 
Wow, that was the fastest response to a bug report I have ever seen! What is the SVN code? Thanks,Walter
Comment 4 Nicholas Nethercote 2005-11-03 23:46:32 UTC 
See http://www.valgrind.org/downloads/repository.html
Comment 5 Tom Hughes 2005-11-08 13:57:16 UTC 
Did you manage to try this with the SVN version? For what it's worth it seems to run on my machine with a current build of valgrind.
Comment 6 Julian Seward 2005-11-16 17:38:01 UTC 
Closing.  If it's still a problem in 3.1.0 we can reopen it.