From: Jakub Jelinek <jakub@redhat.com>
To: davidm@hpl.hp.com
Cc: Ulrich Drepper <drepper@redhat.com>, libc-hacker@sources.redhat.com
Subject: Re: fix ia64 longjmp() to work from alternate signal-stack
Date: Tue, 31 Aug 2004 16:20:00 -0000 [thread overview]
Message-ID: <20040831135945.GJ30497@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <16692.41948.53308.392397@napali.hpl.hp.com>
On Tue, Aug 31, 2004 at 09:14:20AM -0700, David Mosberger wrote:
> So you want me to create an ia64-specific version of __libc_longjmp()
> which will be sigaltstack-safe while everything else goes to
> the old longjmp implementation, right?
>
> The only callers of __libc_longjmp() I found are:
>
> ./linuxthreads/sysdeps/pthread/ptlongjmp.c: __libc_longjmp (env, val);
> ./nptl/sysdeps/pthread/pt-longjmp.c: __libc_longjmp (env, val);
> ./nptl/unwind.c: __libc_longjmp ((struct __jmp_buf_tag *) buf->cancel_jmp_buf, 1);
> ./nptl/unwind.c: __libc_longjmp ((struct __jmp_buf_tag *) ibuf->cancel_jmp_buf, 1);
>
> so I think this would have the desired effect.
The first two should use the old longjmp implementation, the latter
two the sigaltstack-safe one.
Jakub
next prev parent reply other threads:[~2004-08-31 16:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 16:39 David Mosberger
2004-08-26 9:24 ` Ulrich Drepper
2004-08-26 9:37 ` David Mosberger
2004-08-31 15:10 ` David Mosberger
2004-08-31 15:31 ` Ulrich Drepper
2004-08-31 16:14 ` David Mosberger
2004-08-31 16:20 ` Ulrich Drepper
2004-08-31 16:20 ` Jakub Jelinek [this message]
2004-09-01 8:52 ` David Mosberger
2004-09-02 22:50 ` Ulrich Drepper
2004-09-07 17:36 ` David Mosberger
2004-09-13 17:36 ` David Mosberger
2004-09-13 18:39 ` Ulrich Drepper
2004-09-14 17:01 ` David Mosberger
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=20040831135945.GJ30497@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=drepper@redhat.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).