https://bugs.kde.org/show_bug.cgi?id=437571
--- Comment #2 from Jacob <domaga...@gmail.com> ---
Hello Milian, thank you for replying.
It seems to be reproducable with following docker image:
------------------------------------------------------------------
FROM ubuntu:latest
ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get update && apt-get install -y heaptrack gdb clang-11
------------------------------------------------------------------
1. docker run --cap-add=SYS_PTRACE --security-opt seccomp=unconfined
2. Create file test.cc with following content:
-------------------------------
int main(int argc, char** argv)
{
while(1){
int* a = new int(10);
delete a;
}
return 0;
}
-------------------------------
3. Build it 'clang++-11 test.cc -o test'
4. Start it and get its PID
5. Attach heaptrack using the PID 'heaptrack -d -p PID'
6. Heaptrack output:
heaptrack output will be written to "//heaptrack.test.1481.gz"
injecting heaptrack into application via GDB, this might take some time...
Attaching to process 1162
Reading symbols from /test...
(No debugging symbols found in /test)
Reading symbols from /lib/x86_64-linux-gnu/libstdc++.so.6...
(No debugging symbols found in /lib/x86_64-linux-gnu/libstdc++.so.6)
Reading symbols from /lib/x86_64-linux-gnu/libm.so.6...
Reading symbols from /usr/lib/debug//lib/x86_64-linux-gnu/libm-2.31.so...
Reading symbols from /lib/x86_64-linux-gnu/libgcc_s.so.1...
(No debugging symbols found in /lib/x86_64-linux-gnu/libgcc_s.so.1)
Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...
Reading symbols from /usr/lib/debug//lib/x86_64-linux-gnu/libc-2.31.so...
Reading symbols from /lib64/ld-linux-x86-64.so.2...
(No debugging symbols found in /lib64/ld-linux-x86-64.so.2)
__GI___libc_malloc (bytes=4) at malloc.c:2940
2940 malloc.c: No such file or directory.
Symbols already loaded for /lib/x86_64-linux-gnu/libc.so.6
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Symbols already loaded for /usr/lib/heaptrack/libheaptrack_inject.so
Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
The program being debugged was signaled while in a function called from GDB.
GDB remains in the frame where the signal was received.
To change this behavior use "set unwindonsignal on".
Evaluation of the expression containing the function
(heaptrack_inject) will be abandoned.
When the function is done executing, GDB will silently stop.
(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 0x00007f50eb626049 in
std::thread::_M_start_thread(std::unique_ptr<std::thread::_State,
std::default_delete<std::thread::_State> >, void (*)()) () from
/lib/x86_64-linux-gnu/libstdc++.so.6
#2 0x00007f50eb1e66ff in ?? () from /usr/lib/heaptrack/libheaptrack_inject.so
#3 0x00007f50eb1e7ffe in heaptrack_init () from
/usr/lib/heaptrack/libheaptrack_inject.so
#4 0x00007f50eb1e53f2 in heaptrack_inject () from
/usr/lib/heaptrack/libheaptrack_inject.so
#5 <function called from gdb>
#6 __GI___libc_malloc (bytes=4) at malloc.c:2940
#7 0x00007f50eb5f9c29 in operator new(unsigned long) () from
/lib/x86_64-linux-gnu/libstdc++.so.6
#8 0x0000000000401160 in main ()
(gdb)
--
You are receiving this mail because:
You are watching all bug changes.
