https://bugs.kde.org/show_bug.cgi?id=487639
--- Comment #1 from Milian Wolff <m...@milianw.de> ---
is docker important for reproducing this? when I try this locally it just works
as expected. I fear you'll have to debug this on your end so we can see where
it fails.
terminal 1:
```
$ heaptrack -p $(pidof kwrite)
heaptrack output will be written to "/tmp/heaptrack.kwrite.27448.zst"
injecting heaptrack into application via GDB, this might take some time...
NOTE: heaptrack detected DEBUGINFOD_URLS but will disable it to prevent
unintended network delays during recording
If you really want to use DEBUGINFOD, export HEAPTRACK_ENABLE_DEBUGINFOD=1
injection finished
```
terminal 2:
```
$ ps aux | grep heap
milian 27448 0.0 0.0 8048 5412 pts/0 S+ 21:56 0:00 /bin/sh
/mnt/data1/milian/compiled/other/bin/heaptrack -p 27411
...
$ kill 27448
```
terminal 1:
```
removing heaptrack injection via GDB, this might take some time...
heaptrack stats:
allocations: 82
leaked allocations: 7
temporary allocations: 31
Heaptrack finished! Now run the following to investigate the data:
heaptrack --analyze "/tmp/heaptrack.kwrite.27448.zst"
heaptrack_gui detected, automatically opening the file...
```
does it work when you use 'ctrl+c' directly to send the signal to the whole
process group instead of just the bash script individually?
do you see any output on the CLI when sending the signal?
--
You are receiving this mail because:
You are watching all bug changes.
