🚀 go-pugleaf

I have an application that is killed (I assume by the OS). I wanted to
try and figure out what was going on using the casevision debugger.
I was unable to figure out a way to catch the kill, and when the program
mysteriously dies, all I get in the debugger is process xxxx: terminated.

Is there a way to catch the kill signal with the casevision debugger?
With other signals (like INT) when set it in the signal panel, and then
send the application (attached process) an INT, it happily catches it.
And I can look at the stack, etc, etc.

When I set SIGKILL in the signal panel, and then send kill -9 xxxx, 
the process just terminates. [This also happens when the OS does it
to me].

Have I missed something?

Mark.
P.S. I love the debugger. Can't imagine doing C development without it!