Subject: Re: commit -- segfault handler on Unix
From: sam th (sam@uchicago.edu)
Date: Thu Jul 13 2000 - 17:30:35 CDT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 13 Jul 2000, Aaron Lehmann wrote:
> > 5) Should this catch other signals (SIGTERM, the bus error signal, etc)?
>
> The general behaviour that I have seen is that when the program is kill'd,
> it should be the equivilent to the user quitting it.
Does this mean we should prompt the user to save? I don't like that
idea. I think we should handle all signals that terminate the program
(SIGTERM, SIGBUS?, SIGABRT, ...) with the backup that I do for SIGSEGV.
The non-terminating signals (SIGSTOP, SIGTSTP) should be left alone.
SIGKILL can't be caught (neither can SIGSTOP, but that doesn't matter).
sam th
sam@uchicago.edu
http://www.abisource.com/~sam/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE5bkMNt+kM0Mq9M/wRAnNoAKCokPanBJIIxgs6eWwRSUuIK2utmgCfV3lb
Hu2f+ByH0diDLErhFHv9MKM=
=toml
-----END PGP SIGNATURE-----
This archive was generated by hypermail 2b25 : Thu Jul 13 2000 - 16:26:46 CDT