How to Write a Heap Memory Profiler - Milian Wolff - CppCon 2019

[@sourabhforu]

I dont know if there is some value-add of doing this stuff by hand, and not using a standard profiler like valgrind? (apart from great learning ofcourse)

[@lukaszmmaciejewski]

not sure if you’re still interested in the answer after 3 years, but the value added is speed - with heaptrack there is slowdown, but the app being tracked is still somewhat usable in a production environment whereas with valgrind the performance drop is often a blocker for a long production scenario; plus with heaptrack you can runtime-attach

[@afigegoznaet]

Great stuff, thanks

[@thelatestartosrs]

27:20 the digger we deep

The malloc wrapper cannot possibly be so simple :D dlsym can actually call malloc inside, which makes it a bit annoying.

[@tophyr]

dlsym is usually implemented inside the linker executable itself, which is (necessarily) statically-linked and thus wouldn't ever cause a recursion with a wrapped malloc implementation.