News for hackers. Stuff that matters.
Re:Hunting down a C memory leak in a Go program by matt123456789 on Saturday October 16, 2021 @02:31AM (#28885969)
The author describes using eBPF to trace malloc/free refs as a solution to the program properly freeing all heap objects before exiting, which was enlightening to me. Would it have been possible to issue a kill -9 to the program in the middle of execution while using valgrind to see this info as well? Or is it more to the point that eBPF is cleaner and allows you to see many more snapshots of memory allocations while the program is still running?
Re:Hunting down a C memory leak in a Go program by xerxes901 on Saturday October 16, 2021 @02:55AM (#28886069)
Off the top of my head I don't think this would work, because Valgrind needs the atexit hooks to run?

Probably some other signal that has a default action of terminate the program that our app isn't handling might've worked though.