>>> Some small mmap() calls seem to work, but the large mmap(), for an 80GB
>>> file, results in EINVAL

> He said 80GB, not 80MB, so I assume it's already on x86-64.  That's a pretty 
> big file -- not much in a 64-bit address space, admittedly -- but it may be 
> big enough to cause Valgrind problems, not sure.

Oops, you're right. I mis-read the size as 80 megabytes instead of 80 gigabytes.

It still might help to inspect /proc/<pid>/maps.  Also /proc/meminfo (to see
the general state of system memory), and an actual strace of the app running
under memcheck leading up to the failure (to see what valgrind's address
space manager actually did.)

-- 

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to