This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: fix ia64 longjmp() to work from alternate signal-stack

From: Ulrich Drepper <drepper at redhat dot com>
To: davidm at hpl dot hp dot com
Cc: libc-hacker at sources dot redhat dot com, davidm at napali dot hpl dot hp dot com
Date: Tue, 31 Aug 2004 09:20:12 -0700
Subject: Re: fix ia64 longjmp() to work from alternate signal-stack
Organization: Red Hat, Inc.
References: <16684.49335.802840.212013@napali.hpl.hp.com> <412DAC31.1050404@redhat.com> <16692.38122.52348.850833@napali.hpl.hp.com> <413499B2.2030900@redhat.com> <16692.41948.53308.392397@napali.hpl.hp.com>

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?

Basically, yes.  Not sure we should keep the name, though.  And even for
other archs, we might have to reset the stack.  Even though the current
code might everywhere in the moment does not mean it is correct.

-- 
â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â

References:
- fix ia64 longjmp() to work from alternate signal-stack
  - From: David Mosberger
- Re: fix ia64 longjmp() to work from alternate signal-stack
  - From: Ulrich Drepper
- Re: fix ia64 longjmp() to work from alternate signal-stack
  - From: David Mosberger
- Re: fix ia64 longjmp() to work from alternate signal-stack
  - From: Ulrich Drepper
- Re: fix ia64 longjmp() to work from alternate signal-stack
  - From: David Mosberger

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]