| Summary: | padding mmap failed during startup | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Michael Bunk <kleinerwurm> |
| Component: | general | Assignee: | Julian Seward <jseward> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | major | ||
| Priority: | NOR | ||
| Version First Reported In: | 2.4 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Sorry, my fault! ulimit -a revealed my virtual memory limit to me. |
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.