https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64478
--- Comment #18 from Bernd Edlinger <bernd.edlinger at hotmail dot de> --- Hi Eric, if I use kill -11, I would be really surprised to see the process freeze. It would be good to look at siginfo->si_code and _not_ continue the normal exception handling when the si_code is SI_USER or anything <= 0. If you receive a signal 11, with si_code == SI_USER, you can be sure that is sent directly from me, and I want the process to immediately stop doing what it does currently and create a core file for later analysis. I found a pointer in the internet, how to handle SIGSEGV and still create a code file, sounds interesting. http://www.alexonlinux.com/how-to-handle-sigsegv-but-also-generate-core-dump The idea is to just set the signal hander back to default and raise the signal again. Bernd.
