|ABORT(3P)||POSIX Programmer's Manual||ABORT(3P)|
The abort() function shall cause abnormal process termination to occur, unless the signal SIGABRT is being caught and the signal handler does not return.
The abnormal termination processing shall include the default actions defined for SIGABRT and may include an attempt to effect fclose() on all open streams.
The SIGABRT signal shall be sent to the calling process as if by means of raise() with the argument SIGABRT.
The status made available to wait(), waitid(), or waitpid() by abort() shall be that of a process terminated by the SIGABRT signal. The abort() function shall override blocking or ignoring the SIGABRT signal.
The following sections are informative.
The revised wording permits some backwards-compatibility and avoids a potential deadlock situation.
The Open Group Base Resolution bwg2002‐003 is applied, removing the following XSI shaded paragraph from the DESCRIPTION:
``On XSI-conformant systems, in addition the abnormal termination processing shall include the effect of fclose() on message catalog descriptors.''
There were several reasons to remove this paragraph:
- No special processing of open message catalogs needs to be performed prior to abnormal process termination.
- The main reason to specifically mention that abort() includes the effect of fclose() on open streams is to flush output queued on the stream. Message catalogs in this context are read-only and, therefore, do not need to be flushed.
- The effect of fclose() on a message catalog descriptor is unspecified. Message catalog descriptors are allowed, but not required to be implemented using a file descriptor, but there is no mention in POSIX.1‐2008 of a message catalog descriptor using a standard I/O stream FILE object as would be expected by fclose().
The Base Definitions volume of POSIX.1‐2017, <stdlib.h>
Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .
|2017||IEEE/The Open Group|