Re: Exit status

[John Darrington]

This seems to have the effect of producing the bug_report message
twice - the second time, the "proximate cause" is "unknown".

If (say) SIGSEGV is re-raised, the default behaviour is to terminate.
But so far as I'm aware, the exit status is not documented.



On Sat, Oct 02, 2010 at 10:21:55AM -0700, Ben Pfaff wrote:
     John Darrington <address@hidden> writes:
     
     > I think that the exit status in the function request_bug_report_and_abort
     > should be something which is neither EXIT_FAILURE nor EXIT_SUCCESS.  We
     > need an EXIT_CATASTROPHY
     
     The customary way to do this is to re-raise the signal that
     caused the failure, so that the calling process sees that signal.
     
     I pushed this:
     

-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://pgp.mit.edu or any PGP keyserver for public key.

signature.asc
Description: Digital signature