https://bugs.kde.org/show_bug.cgi?id=378494
Milian Wolff <m...@milianw.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |CONFIRMED
--- Comment #1 from Milian Wolff <m...@milianw.de> ---
Confirmed, can reproduce. I'll try to write a proper test for this and fix it,
once I get the time for that.
More information from Maxim that I think is valuable tohave here:
This happens even if the heaptrack_preload.so is injected manually
(so the heaptrack script is not involved); could not get any further.
Under gdb see this:
terminal 1 $ heaptrack ./a.out
heaptrack output will be written to
"/home/centos/work/heaptrack-eval/heaptrack.a.out.22665.gz"
starting application, this might take some time...
Started, press Ctrl-C to abort
(switch to terminal 2) $ gdb ./a.out `pidof a.out`
(gdb) handle SIGTERM nostop pass
Signal Stop Print Pass to program Description
SIGTERM No Yes Yes Terminated
(gdb) c
Continuing.
# in terminal 3: kill -TERM `pidof a.out`
[Thread 0x7fe831af1700 (LWP 22683) exited]
[Thread 0x7fe833b31780 (LWP 22681) exited]
[Inferior 1 (process 22681) exited normally]
(gdb)
In terminal 1:
Interrupted
Done.
heaptrack stats:
allocations: 2
leaked allocations: 1
temporary allocations: 0
Heaptrack finished! Now run the following to investigate the data:
heaptrack_print
"/home/centos/work/heaptrack-eval/heaptrack.a.out.22665.gz" | less
So under GDB the signal is passed to the debuggee correctly if gdb is set
up for that.
--
You are receiving this mail because:
You are watching all bug changes.
