Re: 9.1: forcible coredump -> panic

[Mouse <mouse%Rodents-Montreal.ORG@localhost>]

>> I'm trying to add a deadman timer facility to 9.1's kernel which,
>> from a function called by a callout firing, forcibly coredumps a
>> particular process (which I want to do even if the process is
>> blocking or ignoring normally-core-generating signals):

> A different plan of action might be to manipulate the signal mask so
> that the process doesn't block/ignore the signal, and then send a
> coredump-causing signal.

I thought of that.  But I'm also not sure I want to kill the process.
My current version does, but for the eventual application it may be
better to do something else.  The only option that comes to mind at the
moment would be to forcibly re-exec its binary, but that is heavily
influenced by the motivating use case; I can think of some other things
that might be useful for other use cases, such as sending the victim a
signal, or bashing a memory location in userland....

Also, it looked like an interesting thing to try. :-)

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		mouse%rodents-montreal.org@localhost
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B