Re: [Valgrind-users] mmap failed on

[Nicholas N. <nj...@ca...>]

On Mon, 31 Jan 2005, smiley glitter wrote:

> My executable reaches 900MB when built with debug
> information and can grow more. Though increasing the
> space alloted to valgrind proved helpful (see mail at
> the bottom - same as comment #1 in bug) it reduces the
> space for the client. So either no debug info or no
> memcheck was my situation.
>
> Reading the symbols and debug info from the executable
> happens before execution of the client program. So I
> tried a mmap of the executable in the client space
> instead of valgrind's space to read symbols.

That may be true for the initial executable, but when .so files are loaded 
later, the client is already running.

> Should we bother about a client and valgrind memory
> split as there is no client yet at this stage.

Probably a better way to do this is to incrementally load the debug 
information, rather than mapping in the entire file.  I've added a note to 
bug #82301 about this.

N