https://bugs.kde.org/show_bug.cgi?id=378494
Milian Wolff <m...@milianw.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Latest Commit| |https://commits.kde.org/hea
| |ptrack/e203d56632b94e6607d6
| |cdc8710f947d644fc764
Resolution|--- |FIXED
--- Comment #10 from Milian Wolff <m...@milianw.de> ---
Git commit e203d56632b94e6607d6cdc8710f947d644fc764 by Milian Wolff.
Committed on 07/04/2017 at 12:24.
Pushed by mwolff into branch 'master'.
Disable signal handling in timer thread
When the host application sets up a custom signal handler thread
only that thread is supposed to handle the signals. But heaptrack
spawns up the timer thread on initialization, i.e. when it
first encounters a memory allocation. This usually happens before
the host application has setup the signal mask. As such, our timer
thread would still receive e.g. SIGTERM and then shutdown the whole
application.
Now, we disable signal handling in the helper thread to fix this
behavior for applications that rely on it.
M +24 -0 src/track/libheaptrack.cpp
M +3 -0 tests/manual/CMakeLists.txt
A +110 -0 tests/manual/signals.cpp [License: LGPL (v2+)]
https://commits.kde.org/heaptrack/e203d56632b94e6607d6cdc8710f947d644fc764
--
You are receiving this mail because:
You are watching all bug changes.
