From: Andrew Haley <aph@redhat.com>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: java@gcc.gnu.org
Subject: Re: [patch] Fix oddity in personality routine
Date: Fri, 13 Nov 2009 17:57:00 -0000 [thread overview]
Message-ID: <4AFD9DEF.7050305@redhat.com> (raw)
In-Reply-To: <200911131850.03946.ebotcazou@adacore.com>
Eric Botcazou wrote:
> Hi,
>
> r128098 has introduced an oddity in the personality routine:
>
> int ip_before_insn = 0;
> [...]
>
> // Parse the LSDA header.
> p = parse_lsda_header (context, language_specific_data, &info);
> #ifdef HAVE_GETIPINFO
> ip = _Unwind_GetIPInfo (context, &ip_before_insn);
> #else
> ip = _Unwind_GetIP (context) - 1;
> #endif
> if (! ip_before_insn)
> --ip;
>
> So, if !HAVE_GETIPINFO, the IP is decremented by 2! It used to be 1 and both
> libstdc++-v3/libsupc++/eh_personality.cc and ada/raise-gcc.c have the expected
> version:
>
> #ifdef _GLIBCXX_HAVE_GETIPINFO
> ip = _Unwind_GetIPInfo (context, &ip_before_insn);
> #else
> ip = _Unwind_GetIP (context);
> #endif
> if (! ip_before_insn)
> --ip;
>
> Hence the attached patch, that I don't plan to test though. OK anyway?
>
>
> 2009-11-13 Eric Botcazou <ebotcazou@adacore.com>
>
> * exception.cc (PERSONALITY_FUNCTION): Fix oversight.
>
Yes, I think that's right.
Andrew.
next prev parent reply other threads:[~2009-11-13 17:57 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 17:49 Eric Botcazou
2009-11-13 17:57 ` Andrew Haley [this message]
2009-11-13 18:36 ` Jack Howarth
2009-11-13 18:39 ` Andrew Haley
2009-11-13 19:18 ` Jack Howarth
2009-11-15 23:02 ` Bryce McKinlay
2009-11-16 14:22 ` Jack Howarth
2009-11-16 15:12 ` Jack Howarth
2009-11-16 15:17 ` Andrew Haley
2009-11-16 15:34 ` Jack Howarth
2009-11-16 16:59 ` Andrew Haley
2009-11-16 18:07 ` Jack Howarth
2009-11-16 19:10 ` Andrew Haley
2009-11-16 19:48 ` Jack Howarth
2009-11-17 0:48 ` Jack Howarth
2009-11-17 10:59 ` Andrew Haley
2009-11-17 14:05 ` Jack Howarth
2009-11-17 14:56 ` Andrew Haley
2009-11-17 16:18 ` Jack Howarth
2009-11-17 16:22 ` Andrew Haley
2009-11-17 17:07 ` Jack Howarth
2009-11-17 17:14 ` Andrew Haley
2009-11-17 17:38 ` Jack Howarth
2009-11-27 10:37 ` borlum
2009-11-27 10:40 ` Andrew Haley
2009-11-27 10:52 ` borlum
2009-11-27 14:20 ` Bryce McKinlay
2009-11-27 16:29 ` Jack Howarth
2009-11-27 21:51 ` Jack Howarth
2009-11-28 10:43 ` Andrew Haley
2009-11-29 17:48 ` Jack Howarth
2009-11-29 18:01 ` Andrew Haley
2009-11-29 18:48 ` Jack Howarth
2009-11-30 10:09 ` Andrew Haley
2009-11-30 16:01 ` Jack Howarth
2009-11-30 16:07 ` Andrew Haley
2009-12-01 5:02 ` Jack Howarth
2009-12-01 9:30 ` Andrew Haley
2009-12-01 17:04 ` Jack Howarth
2009-12-01 17:24 ` Andrew Haley
2009-12-01 23:29 ` Jack Howarth
2009-12-02 9:34 ` Andrew Haley
2009-12-03 1:08 ` Jack Howarth
2009-12-03 10:26 ` Andrew Haley
2009-12-03 14:03 ` Jack Howarth
2009-12-03 14:10 ` Andrew Haley
2009-12-03 19:18 ` Boehm, Hans
2009-12-03 21:25 ` Andrew Haley
2009-12-04 3:01 ` Jack Howarth
2009-12-04 9:45 ` Andrew Haley
2009-12-04 4:12 ` Jack Howarth
2009-12-04 9:44 ` Andrew Haley
2009-12-04 14:51 ` Jack Howarth
2009-12-04 14:59 ` Andrew Haley
2009-12-04 15:23 ` Jack Howarth
2009-12-04 15:48 ` Andrew Haley
2009-12-04 15:57 ` Bryce McKinlay
2009-12-05 4:37 ` Jack Howarth
2009-12-05 6:54 ` Jack Howarth
2009-12-04 15:59 ` Jack Howarth
2009-12-04 16:06 ` Andrew Haley
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=4AFD9DEF.7050305@redhat.com \
--to=aph@redhat.com \
--cc=ebotcazou@adacore.com \
--cc=java@gcc.gnu.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).