[Valgrind-users] More than 32GB memory

[Christoph B. <bar...@or...>]

Hi,

I am currently debugging an application that needs more than 32GB memory. 
Valgrind however does not allow me to allocate more. I get the following 
message:

     Valgrind's memory management: out of memory:
        newSuperblock's request for 660615168 bytes failed.
        34312749056 bytes have already been allocated.
     Valgrind cannot continue.  Sorry.

     There are several possible reasons for this.
     - You have some kind of memory limit in place.  Look at the
       output of 'ulimit -a'.  Is there a limit on the size of
       virtual memory or address space?
     - You have run out of swap space.
     - Valgrind has a bug.  If you think this is the case or you are
     not sure, please let us know and we'll try to fix it.
     Please note that programs can take substantially more memory than
     normal when running under Valgrind tools, eg. up to twice or
     more, depending on the tool.  On a 64-bit machine, Valgrind
     should be able to make use of up 32GB memory.  On a 32-bit
     machine, Valgrind should be able to use all the memory available
     to a single process, up to 4GB if that's how you have your
     kernel configured.  Most 32-bit Linux setups allow a maximum of
     3GB per process.


Is there a way to increase the memory allocation limit for valgrind? 200 GB 
would be enough.

Greetings
Christoph