https://bugs.kde.org/show_bug.cgi?id=397476
--- Comment #3 from Damian Szuberski <szuberskidam...@gmail.com> ---
Thank your for fast reaction.
$ cat main.cpp
#include <iostream>
int main()
{
std::cout << new int(6) << std::endl;
}
$ g++ -g -o main main.cpp
$ heaptrack ./main
$ heaptrack_print /home/szubersk/tmp/heaptrack/a/heaptrack.main.13091.gz | grep
CALLS -A 6
MOST CALLS TO ALLOCATION FUNCTIONS
1 calls to allocation functions with 4B peak consumption from
main
at /home/szubersk/tmp/heaptrack/a/main.cpp:5
in /home/szubersk/tmp/heaptrack/a/main
1 calls with 4B peak consumption from:
$ heaptrack /lib64/ld-linux-x86-64.so.2 ./main
$ heaptrack_print heaptrack.ld-linux-x86-64.so.2.13132.gz | grep CALLS -A 6
MOST CALLS TO ALLOCATION FUNCTIONS
1 calls to allocation functions with 4B peak consumption from
0x7f4d7cd30182
in /lib/x86_64-linux-gnu/ld-2.27.so
1 calls with 4B peak consumption from:
__libc_start_main
in /lib/x86_64-linux-gnu/libc.so.6
In addition please see the screenshot attached to see how visualizer shows that
4B allocation (<unresolved function>).
--
You are receiving this mail because:
You are watching all bug changes.
