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

2022-08-31 Thread Bresalier, Rob (Nokia - US/Murray Hill)
> Normally, if it is the OOM that kills a process, you should find a trace of > this in the system logs. I looked in every system log I could find, there was no indication of OOM killing it in any system log. > I do not understand what you mean by reducing the nr of callers from 12 to 6. >

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

2022-08-31 Thread Philippe Waroquiers
On Wed, 2022-08-31 at 17:42 +, Bresalier, Rob (Nokia - US/Murray Hill) wrote: > > When running memcheck on a massive monolith embedded executable > > (237MB stripped, 1.8GiB unstripped), after I stop the executable under > > valgrind I see the "HEAP SUMMARY" but then valgrind dies before any

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

2022-08-31 Thread Bresalier, Rob (Nokia - US/Murray Hill)
> When running memcheck on a massive monolith embedded executable > (237MB stripped, 1.8GiB unstripped), after I stop the executable under > valgrind I see the "HEAP SUMMARY" but then valgrind dies before any leak > reports are printed. The parent process sees that the return status of > memcheck