Re: memcheck is getting SIGKILLed before leak report is output

"Bresalier, Rob (Nokia - US/Murray Hill)" <[email protected]>
Newsgroups gmane.comp.debugging.valgrind
Message-ID <PH0PR08MB6988114A5345B4CF325E9C44F39E9@PH0PR08MB6988.namprd08.prod.outlook.com> 
> If finding memory leaks is the only goal (for instance, if you are satisfied that
> memcheck has found all the overrun blocks, uninitialized reads, etc.) then
> https://github.com/KDE/heaptrack  is the best tool.  

Thanks! I didn't know about heaptrack. I will look definitely into that. Does heaptrack also show  the 'still reachable' types of leaks that memcheck does?

Any chance that the 'massif' tool would survive the OOM killer? This may be easier for me to get going as I already have valgrind built.

Is there anything that can be done with memcheck to make it consume less memory?
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.