David Powell writes: > Generating an event on abort(3c) makes a lot of sense. > > WRT naked SIGABRTs, the default disposition for SIGABRT is to dump a > core, and core dump events already include the signal number that > caused them. A separate event in this case doesn't buy us much.
That means an application that implements its own abort-like function by kill(0,SIGABRT) and that hooks SIGABRT to do something silly (like generating a traceback in a debug log) won't treat the ensuing exit as a failure. I guess that's just a limitation ... -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
