public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: libc-hacker@sources.redhat.com
Cc: davidm@napali.hpl.hp.com
Subject: what to do about dl_iterate_phdr()
Date: Mon, 19 Apr 2004 18:39:00 -0000	[thread overview]
Message-ID: <16516.7410.677626.450899@napali.hpl.hp.com> (raw)
In-Reply-To: <16492.44824.546092.273252@napali.hpl.hp.com>

dl_iterate_phdr() isn't signal-safe and therefore there is currently
no way to safely unwind out of a signal-handler.  My proposal to make
dl_iterate_phdr() async-signal-safe seems to have fallen on deaf ears.

So what's your position?  Is the official position that glibc simply
cannot safely unwind out of a signal handler or do you have an
alternate proposal in mind?

Thanks,

	--david

      reply	other threads:[~2004-04-19 18:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01  7:50 is dl_iterate_phdr() supposed to be async-signal safe? David Mosberger
2004-04-01 21:22 ` Roland McGrath
2004-04-02  0:09   ` David Mosberger
2004-04-19 18:39     ` David Mosberger [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=16516.7410.677626.450899@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=davidm@hpl.hp.com \
    --cc=libc-hacker@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).