[PATCH] abort: clarify consequences of calling abort

[PATCH] abort: clarify consequences of calling abort

[Tomáš Golembiovský]

Clarify that atexit/on_exit are not called because those are called only
on normal process termination (as documented on their respective manual
pages).

Clarify the status reported by wait*() functions. The requirement comes
from POSIX specification.

Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com>
---
 man3/abort.3 | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/man3/abort.3 b/man3/abort.3
index c63eace5e..6d1638033 100644
--- a/man3/abort.3
+++ b/man3/abort.3
@@ -47,6 +47,16 @@ function will still terminate the process.
 It does this by restoring the default disposition for
 .B SIGABRT
 and then raising the signal for a second time.
+.PP
+As with other cases of abnormal termination the functions registered with
+.BR atexit "(3) and " on_exit (3)
+are not called. The status made available to
+.BR wait "(2), " waitid "(2), or " waitpid (2)
+by
+.BR abort ()
+shall be that of a process terminated by the
+.BR SIGABRT
+signal.
 .SH RETURN VALUE
 The
 .BR abort ()
-- 
2.41.0

Re: [PATCH] abort: clarify consequences of calling abort

[Alejandro Colomar]

[-- Attachment #1.1: Type: text/plain, Size: 1881 bytes --]

On 7/4/23 17:09, Tomáš Golembiovský wrote:
> Clarify that atexit/on_exit are not called because those are called only
> on normal process termination (as documented on their respective manual
> pages).
> 
> Clarify the status reported by wait*() functions. The requirement comes
> from POSIX specification.
> 
> Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com>

Hi Tomáš,

> ---
>   man3/abort.3 | 10 ++++++++++
>   1 file changed, 10 insertions(+)
> 
> diff --git a/man3/abort.3 b/man3/abort.3
> index c63eace5e..6d1638033 100644
> --- a/man3/abort.3
> +++ b/man3/abort.3
> @@ -47,6 +47,16 @@ function will still terminate the process.
>   It does this by restoring the default disposition for
>   .B SIGABRT
>   and then raising the signal for a second time.
> +.PP
> +As with other cases of abnormal termination the functions registered with
> +.BR atexit "(3) and " on_exit (3)
> +are not called. The status made available to

Please use semantic newlines.  See man-pages(7):
    Use semantic newlines
        In  the  source of a manual page, new sentences should be
        started on new lines, long sentences should be split into
        lines at clause breaks (commas, semicolons,  colons,  and
        so on), and long clauses should be split at phrase bound‐
        aries.   This  convention,  sometimes  known as "semantic
        newlines", makes it easier to see the effect of  patches,
        which often operate at the level of individual sentences,
        clauses, or phrases.

Thanks,
Alex

> +.BR wait "(2), " waitid "(2), or " waitpid (2)
> +by
> +.BR abort ()
> +shall be that of a process terminated by the
> +.BR SIGABRT
> +signal.
>   .SH RETURN VALUE
>   The
>   .BR abort ()

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]