public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "Tomáš Golembiovský" <tgolembi@redhat.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] abort: clarify consequences of calling abort
Date: Sat, 8 Jul 2023 19:07:46 +0200	[thread overview]
Message-ID: <3910b44d-d015-06ca-e774-f754e56a137f@kernel.org> (raw)
In-Reply-To: <a1efcd54c02faa51a7a25b9211b3f1f6bd38429f.1688483306.git.tgolembi@redhat.com>


[-- 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 --]

      reply	other threads:[~2023-07-08 17:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 15:09 [PATCH] abort: clarify consequences of calling abort Tomáš Golembiovský
2023-07-08 17:07 ` Alejandro Colomar [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3910b44d-d015-06ca-e774-f754e56a137f@kernel.org \
    --to=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=tgolembi@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox