[Heaptrack] [Bug 409606] Track memory allocated with mmap

2021-05-04 Thread Andrew Somerville
https://bugs.kde.org/show_bug.cgi?id=409606 --- Comment #12 from Andrew Somerville --- I created https://github.com/catskul/tizen-heaptrack to make comparison, PRs, and forking easier. I'll take a look later to see if there's any twidling I need to do to make it share history with

[Heaptrack] [Bug 409606] Track memory allocated with mmap

2021-04-30 Thread Andrew Somerville
https://bugs.kde.org/show_bug.cgi?id=409606 Andrew Somerville changed: What|Removed |Added CC||andy.somervi...@gmail.com --- Comment #11

[Heaptrack] [Bug 409606] Track memory allocated with mmap

2021-02-24 Thread Pash
https://bugs.kde.org/show_bug.cgi?id=409606 --- Comment #10 from Pash --- (In reply to Milian Wolff from comment #9) > found it: https://git.tizen.org/cgit/sdk/tools/heaptrack/ > > quite sad that they never ever spoke to me, nor even tried to upstream some > of their changes :( I am trying :)

[Heaptrack] [Bug 409606] Track memory allocated with mmap

2021-02-19 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=409606 --- Comment #9 from Milian Wolff --- found it: https://git.tizen.org/cgit/sdk/tools/heaptrack/ quite sad that they never ever spoke to me, nor even tried to upstream some of their changes :( -- You are receiving this mail because: You are watching

[Heaptrack] [Bug 409606] Track memory allocated with mmap

2021-02-19 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=409606 --- Comment #8 from Milian Wolff --- @Pash: do you mean samsung/tizen has forked heaptrack? cool! can you refer me to their code repo? First time I hear about that. -- You are receiving this mail because: You are watching all bug changes.

[Heaptrack] [Bug 409606] Track memory allocated with mmap

2021-02-18 Thread Pash
https://bugs.kde.org/show_bug.cgi?id=409606 Pash changed: What|Removed |Added CC||orehovpa...@gmail.com --- Comment #7 from Pash ---

[Heaptrack] [Bug 409606] Track memory allocated with mmap

2019-10-13 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=409606 --- Comment #6 from Milian Wolff --- nvm that, I forgot to init the mmap hook, it all seems to work fine actually! thanks a lot for bringing this to my attention, I'm seriously wondering why I never tried this out so far. -- You are receiving this

[Heaptrack] [Bug 409606] Track memory allocated with mmap

2019-10-13 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=409606 --- Comment #5 from Milian Wolff --- Hm yes indeed, I just tested it and I can really intercept it - awesome! I'll definitely want to add that in the future then. I'm not yet sure how to do this properly though, as intercepting mmap may still need some

[Heaptrack] [Bug 409606] Track memory allocated with mmap

2019-10-13 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=409606 Milian Wolff changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0

[Heaptrack] [Bug 409606] Track memory allocated with mmap

2019-10-13 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=409606 --- Comment #4 from tbl...@icloud.com --- There's no mmap symbol in the VDSO. mmap in libc is a wrapper that makes a syscall through the VDSO or directly on some architectures, so you can intercept it. -- You are receiving this mail because: You are

[Heaptrack] [Bug 409606] Track memory allocated with mmap

2019-10-13 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=409606 --- Comment #3 from Milian Wolff --- but the mmap symbol in libc is just a shim that gets replaced by a symbol from the vdso, no? and afaik you cannot intercept these via LD_PRELOAD - or am I mistaken? -- You are receiving this mail because: You are

[Heaptrack] [Bug 409606] Track memory allocated with mmap

2019-07-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=409606 --- Comment #2 from tbl...@icloud.com --- LD_PRELOAD would work at least in my case, since I call mmap through the C library. For times when this doesn't work, intercepting mmap with ptrace is possible, and not all that hard. -- You are receiving this

[Heaptrack] [Bug 409606] Track memory allocated with mmap

2019-07-16 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=409606 --- Comment #1 from Milian Wolff --- syscalls like mmap cannot be easily intercepted with LD_PRELOAD or similar, which makes it quasi impossible to do with the current architecture of heaptrack. thankfully, you can easily use perf to achieve the same,