From: Oleg <lego12239@yandex.ru>
To: 9fans@9fans.net
Subject: Re: [9fans] atexit() & atexitdont()
Date: Fri, 7 Nov 2014 15:19:29 +0300 [thread overview]
Message-ID: <20141107121929.GA10144@localhost> (raw)
In-Reply-To: <CAOw7k5iGCvOeaaLFy99UC+5JMLTSq9T4Cj0D=3p5S-QQfnmyAQ@mail.gmail.com>
On Fri, Nov 07, 2014 at 11:49:08AM +0000, Charles Forsyth wrote:
> On 7 November 2014 10:57, Steffen Nurpmeso <sdaoden@yandex.com> wrote:
>
> > Safety against asynchronous un-/registration can't be it, anyway.
>
>
> No, there's a lock. I meant avoiding too many possible interactions between
> low-level run-time
> functions and the rest of the library. (I'd consider atexit and exit to be
> lower-level functions than malloc.)
> Since atexit is already used by profile, and is called by _profmain, which
> is called very early on,
> putting a call to malloc in that chain means you have to think that much
> harder about interactions that are already quite subtle.
This is an interesting. With this info the array reordering in atexitdont()
looks good comparing to malloc in atexit().
next prev parent reply other threads:[~2014-11-07 12:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 21:05 Oleg
2014-11-06 21:26 ` erik quanstrom
2014-11-06 21:42 ` Skip Tavakkolian
2014-11-06 21:44 ` Skip Tavakkolian
2014-11-06 22:50 ` lego12239
2014-11-06 22:45 ` Oleg
2014-11-07 7:17 ` k0ga
2014-11-07 8:02 ` Oleg
2014-11-07 8:19 ` Charles Forsyth
2014-11-07 9:44 ` Oleg
2014-11-07 10:22 ` Charles Forsyth
2014-11-07 11:05 ` Oleg
2014-11-07 10:57 ` Steffen Nurpmeso
2014-11-07 11:49 ` Charles Forsyth
2014-11-07 12:19 ` Oleg [this message]
2014-11-07 12:27 ` Charles Forsyth
2014-11-07 19:53 ` erik quanstrom
2014-11-07 20:30 ` Oleg
2014-11-07 19:25 ` Steffen Nurpmeso
2014-11-07 17:45 sl
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=20141107121929.GA10144@localhost \
--to=lego12239@yandex.ru \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).