public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: GLIBC Devel <libc-alpha@sourceware.org>
Subject: Re: [patch] Add tests for atexit/on_exit firing order
Date: Mon, 10 Jul 2017 15:18:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.20.1707101515450.30742@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CALoOobMo+n2qfftAYG6Tyibg7Y7iCDn0PEMuBhvJyzwT4vVxZA@mail.gmail.com>

On Mon, 10 Jul 2017, Paul Pluzhnikov wrote:

> Greetings,
> 
> While working a on patch for bz14333, I discovered that there are no
> tests for ordering of functions registered with atexit/on_exit, and in
> particular the case where such function itself registers new exit
> handlers.
> 
> This patch adds such test. I am using on_exit here because it
> conveniently allows passing an argument.

I'd think that it would make sense to test all of atexit, on_exit, 
at_quick_exit this way.

-- 
Joseph S. Myers
joseph@codesourcery.com

  parent reply	other threads:[~2017-07-10 15:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10 15:01 Paul Pluzhnikov
2017-07-10 15:09 ` Carlos O'Donell
2017-07-10 15:18 ` Joseph Myers [this message]
2017-07-10 15:39   ` Paul Pluzhnikov
2017-07-10 15:45     ` Szabolcs Nagy
2017-07-10 15:56       ` Joseph Myers
2017-07-24 15:50         ` Paul Pluzhnikov
2017-07-24 17:05           ` Paul Pluzhnikov
2017-07-31 18:05             ` Paul Pluzhnikov
2017-08-07 14:54               ` Paul Pluzhnikov
2017-08-16 16:36             ` Carlos O'Donell
2017-08-28  2:16               ` Paul Pluzhnikov
2017-07-10 15:55     ` Joseph Myers

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=alpine.DEB.2.20.1707101515450.30742@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=ppluzhnikov@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).