PRIORITY: should this be unsigned instead of int?

fixed by using an updated libbacktrace

code review is taking place on github for this change request: https://github.com/KDE/heaptrack/pull/12

I see from your recent commits that you've figured most things out here.

I've adapted and pushed this now. Many thanks Ivan! Much appreciated.

Aha, -DTAKE_ADDR fails when I use ld.bfd instead of ld.gold, I assume you do that too? I still don't see a difference with using -Wl,-z,now though...

I fail to reproduce the issue with the provided test case on ArchLinux. When I compile the three variants, I always properly detect the free calls.

Thanks, I'll take over then. What email address should I use to attribute (parts of) the patch to?

I was curious enough to figure out what compiler behavior causes the different type of relocation entries, so here's a test program with extensive comments. I was originally seeing the behavior with libcairo, but this should make testing easy.

I'm not much of a C++ guy, so take it from here, Milian, if this patch still needs work. :)

hey, thanks for the contribution! do you have a code snippet that showed the behavior we could use for testing purposes?

abandoning since https://phabricator.kde.org/D7621 got landed

taking over to close

thanks, I'll fix this up and merge this

Added link to bug 383889.

I opened https://phabricator.kde.org/D7621 which includes the requested changes.

Please also add a link to https://bugs.kde.org/show_bug.cgi?id=383889

A WIP for this can be found in wip/buildid, it will include the buildid in the heaptrack file. But for interpreting, it isn't enough to just load the debug file only. It has to be used in addition apparently, which isn't possible without patching libbacktrace like is done in vogl.

some ideas on how to do it:

need to add configuration for the editor preferences, similar to what gammaray does

additionally, we could try to use seccomp(-bpf) to get notified about mmap syscalls via SIGSYS, but I'm not sure whether we get access to the syscall args from the interrupt handler

there's now a public heaptrack_api.h for pool allocators.

implemented now

implemented now

implemented now with

On a 32bit machine:

We should look at rr, and how they monkey-patch the vdso to trace all syscalls. That could be used then to track I/O and futex stuff. It would also be useful for heaptrack itself to trace mmap/munmap/sbrk to check heapspace vs. the "real" requested memory by the allocator.

Also an option: http://diamon.org/ctf/

good inspiration: https://en.wikipedia.org/wiki/LEB128