Bug 105789 - padding mmap failed during startup
Summary: padding mmap failed during startup
Status: RESOLVED WORKSFORME
Alias: None
Product: valgrind
Classification: Unclassified
Component: general (show other bugs)
Version: 2.4
Platform: Compiled Sources Linux
: NOR major (vote)
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-17 07:19 UTC by Michael Bunk
Modified: 2005-05-17 13:52 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Bunk 2005-05-17 07:19:10 UTC
starting valgrind even without any arguments outputs this message:

> valgrind: padding mmap(0x80f6000, -1477402624) failed during startup.
> valgrind: is there a hard virtual memory limit set?

ulimit gives "unlimited", but the physical RAM is only 128 MB.
500 MB swap space are there.

SuSE 9.0

ulimit -a:
Linux shabijingsngewthuh 2.4.21-243-cyrix3 #5 Thu Dec 30 12:54:59 IST 2004 i686
i686 i386 GNU/Linux

libc 2.3.2 (20030827)

full output of valgrind -v cannot be given.
Comment 1 Michael Bunk 2005-05-17 13:52:47 UTC
Sorry, my fault! ulimit -a revealed my virtual memory limit to me.