From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Ken Werner <ken.werner@linaro.org>, Andrew Haley <aph@redhat.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: ARM Linux EABI: unwinding through a segfault handler
Date: Tue, 30 Aug 2011 15:28:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1108301524170.23667@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAN9gPaHOOuNmNwN04jx5CkFNwPUiwjn9R_1H=XLJ06T3fMnYKw@mail.gmail.com>
On Mon, 29 Aug 2011, Daniel Jacobowitz wrote:
> I thought we used a handler in GLIBC that was properly annotated,
> nowadays, but I might be mistaken.
What we have in GLIBC is
ports/sysdeps/unix/sysv/linux/arm/eabi/sigrestorer.S. Note that
sigaction.c has to check the kernel version to determine which function to
use because 2.6.18 changed the signal frame layout, not realising that it
was part of the userspace ABI.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2011-08-30 15:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 12:26 Andrew Haley
2011-08-25 16:57 ` David Daney
2011-08-25 17:01 ` Andrew Haley
2011-08-29 15:19 ` Ken Werner
2011-08-29 17:14 ` Daniel Jacobowitz
2011-08-30 9:11 ` Andrew Haley
2011-08-30 15:28 ` Joseph S. Myers [this message]
2011-10-27 8:33 ` Paul Brook
2011-10-27 9:06 ` Andrew Haley
2011-10-27 12:54 ` Paul Brook
2011-10-27 12:55 ` Andrew Haley
2011-10-27 13:25 ` Paul Brook
2015-02-03 22:41 ` mads_bn
2015-09-18 15:37 ` Matthijs van Duin
2015-10-03 20:41 ` Matthijs van Duin
2015-10-04 8:05 ` Andrew Haley
2015-10-04 12:09 ` Matthijs van Duin
2015-10-05 15:24 ` Ian Lance Taylor
2015-02-03 22:42 ` mads_bn
2014-08-01 12:25 ` prafullakota
2015-10-04 8:50 SV: " mads_bn
2015-10-04 13:09 ` Matthijs van Duin
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=Pine.LNX.4.64.1108301524170.23667@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=aph@redhat.com \
--cc=drow@false.org \
--cc=gcc@gcc.gnu.org \
--cc=ken.werner@linaro.org \
/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).