Analyze un-instrumented ELF core files for leaks, memory growth and corruption

https://github.com/vmware/chap#readme

by ingve • 9 years ago

67 5 9 years ago

github.com

dman• 9 years ago

Any pointers about the approach used by this tool to catch leaks?

ingve• 9 years ago

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)

revelation• 9 years ago

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).

foobiekr• 9 years ago

As a guess, you can view this as the same problem as a garbage collector for C programs.

gregnbanks• 9 years ago

http://search.cpan.org/~gnb/Devel-Plumber-0.3.4/lib/Devel/Pl...

Analyze un-instrumented ELF core files for leaks, memory growth and corruption

Related Stories