Re: [Valgrind-users] Swap Space Problem

[Olly B. <ol...@su...>]

On Mon, Jun 16, 2003 at 06:57:07PM -0700, John Reiser wrote:
> Mitchell Kang wrote:
> >VG_(get_memory_from_mmap): request for 8192 bytes failed.
> >VG_(get_memory_from_mmap): 2119042790 bytes already allocated.
> > 
> >This may mean that you have run out of swap space,
> >since running programs on valgrind increases their memory
> >usage at least 3 times.
> 
> Insure++ for Linux/x86 has a "no preparation required" checking mode
> which for large processes has a memory overhead factor close to 1/4
> [total usage while monitoring is a factor of about (1 + 1/4) times the
> non-monitored usage].

Is this mode similar to valgrind's --skin=addrcheck?  According to the
documentation, that has an overhead of about 1/8 (compared to 9/8 for
memcheck).

Or does 1/4 mean that it's also tracking validity at the byte level
(rather than at the bit level as memcheck does)?

Cheers,
    Olly