From: Mailer <vine24683579@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] At-exit hook
Date: Thu, 7 Nov 2024 12:27:00 +0000 [thread overview]
Message-ID: <20241107122700.b37d3e8d2c1c09203147117e@gmail.com> (raw)
In-Reply-To: <20241107120925.87d4b80c9f289d18eec437ad@gmail.com>
On Thu, 7 Nov 2024 12:09:25 +0000
Mailer <vine24683579@gmail.com> wrote:
> On Thu, 7 Nov 2024 12:23:08 +0100
> Maxime Devos <maximedevos@telenet.be> wrote:
> > ‘atexit’ functions are run at ‘exit’. ‘exit’ can be run from signal
> > handlers (*). Since the hook runs Scheme code, it could do a lot of
> > AC-unsafe things, resulting in problems.
> >
> > (*) glibc documentation says ‘exit’ is AC-unsafe, but this is
> > unsupported by POSIX AFAICT. OTOH the same applies to even ‘malloc’,
> > so likely I’m looking in the wrong places.
>
> I think you meant async-signal-safe (AS-safe). 'exit' is not a-s-s and
> cannot be called in a signal handler (for example it can flush buffers)
> whereas '_exit' is a-s-s. Furthermore a registered handler cannot
> itself safely call 'exit'.
>
> I believe the main reason that use of 'atexit' or 'on_exit' is
> discouraged is that it does not handle abnormal process termination.
> (Registered handlers also don't run on termination by '_exit', but that
> is usually what you want.)
I believe also that use of 'atexit' is discouraged in dynamically linked
libraries because of the uncertain timing of the unloading of the
library, but I think in fact glibc is OK with this, so I guess it may
depend on your libc.
Chris
next prev parent reply other threads:[~2024-11-07 12:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 19:52 [PATCH] At-exit hook Mikael Djurfeldt
2024-11-07 11:23 ` Maxime Devos
2024-11-07 12:08 ` Nala Ginrut
2024-11-07 12:09 ` Mailer
2024-11-07 12:27 ` Mailer [this message]
2024-11-07 13:28 ` Mikael Djurfeldt
2024-11-07 16:10 ` Maxime Devos
2024-11-07 19:51 ` Mailer
2024-11-07 22:18 ` Maxime Devos
2024-11-08 9:09 ` Mikael Djurfeldt
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241107122700.b37d3e8d2c1c09203147117e@gmail.com \
--to=vine24683579@gmail.com \
--cc=guile-devel@gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).