Re: [Valgrind-users] memcheck is getting SIGKILLed before leak report is output

[John R. <jr...@bi...>]

>> Is there anything that can be done with memcheck to make it consume less memory?
> 
> No.

Well, you can use the command-line argument "--num-callers=<number>" to reduce the length
of tracebacks that are stored in the "red zones" just before and after an allocated block.
This might help enough if you have zillions of "still reachable" blocks.  But you get
shorter tracebacks, which might not give enough information to find and fix the leak
quickly.
If you do not have zillions of "still reachable" blocks, then --num-callers
will not help so much; but probably would not be needed anyway.