David Powell writes: > FYI, I've filed > > 6668167 explicitly generated process contract events > > to cover a possible solution to the general problem of process > failures that cannot be detected by external observers.
You mention assert() in that CR, but I'd argue for both the abort(3C) function and the underlying SIGABRT signal itself to be treated as "special," even when generated inside the process contract. All of these are intentionally used to indicate "something has failed." -- 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
