John Darrington <[email protected]> writes:
> 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.
Oops. I missed adding some "break"s to the switch statement. I
pushed a fix.
> But so far as I'm aware, the exit status is not documented.
If the parent process is a C program, then WIFSIGNALED and
WTERMSIG can be used. If the parent process is a shell script,
then the examples in the POSIX "kill" manpage show how to find
out the exit signal:
http://www.opengroup.org/onlinepubs/009695399/utilities/kill.html
--
Ben Pfaff
http://benpfaff.org
_______________________________________________
pspp-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/pspp-dev
