News for hackers. Stuff that matters.

A comment on Analyze un-instrumented ELF core files for leaks, memory growth and corruption.

Re:Analyze un-instrumented ELF core files for leaks, memory ... by dman on Friday April 28, 2017 @06:18PM (#14223608)
Any pointers about the approach used by this tool to catch leaks?
[ Parent | on HN ]
Re:Analyze un-instrumented ELF core files for leaks, memory ... by ingve on Friday April 28, 2017 @06:44PM (#14223762)
They are giving a presentation at ACCU 2017 tomorrow. [0] I will find out and report back. :)

[0] https://conference.accu.org/site/stories/2017/sessions.html#...

(Apparently chap was previously called ah64)

[ Parent | on HN ]
Re:Analyze un-instrumented ELF core files for leaks, memory ... by revelation on Friday April 28, 2017 @07:57PM (#14224147)
No idea on what this tool does, but I guess you could emulate what a (terrible) GC does and bruteforce stack and memory for valid pointers. You know which pointers are valid from analyzing the heap management info, hence why this only works for glibc malloc (would have to implement on a case by case basis).
[ Parent | on HN ]
Re:Analyze un-instrumented ELF core files for leaks, memory ... by foobiekr on Saturday April 29, 2017 @12:35AM (#14225068)
As a guess, you can view this as the same problem as a garbage collector for C programs.
[ Parent | on HN ]