From: Pedro Alves <palves@redhat.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: Roland Schwingel <roland.schwingel@onevision.de>,
"gdb-patches@sourceware.org ml"
<gdb-patches@sourceware.org>
Subject: Re: [RFA] Windows x64 SEH unwinder (v2)
Date: Thu, 22 Aug 2013 10:22:00 -0000 [thread overview]
Message-ID: <5215E662.5020902@redhat.com> (raw)
In-Reply-To: <E1936B9C-BD6A-4668-8350-A6E02CF08EF0@adacore.com>
On 08/21/2013 02:45 PM, Tristan Gingold wrote:
>
> On Aug 19, 2013, at 6:01 PM, Roland Schwingel <roland.schwingel@onevision.de> wrote:
>
>> Hi Tristan,
>>
>>> I do not have this issue with the compiler installed here.
>>>
>>> Can you send me (privately) your binary ?
>> Sure. Will come in the next couple of minutes.
>
> I think I understand the issue.
>
> This is caused by DW_OP_call_frame_cfa, which is supported only by
> the dwarf2 unwinder.
> This issue has been fixed in gcc (CL date is 2012-03-15).
It took me a bit to dig out which patch that was, to understand
what the issue is. For the benefit of others, it's here:
http://gcc.gnu.org/ml/gcc-patches/2012-03/msg00980.html
--
Pedro Alves
next prev parent reply other threads:[~2013-08-22 10:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 16:01 Roland Schwingel
2013-08-21 13:45 ` Tristan Gingold
2013-08-22 10:22 ` Pedro Alves [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-22 11:22 Roland Schwingel
2013-08-19 15:14 Roland Schwingel
2013-08-19 15:32 ` Tristan Gingold
2013-08-05 11:25 Roland Schwingel
2013-08-19 13:53 ` Tristan Gingold
2013-01-09 10:53 Add Windows x64 SEH unwinder (take 2) Joel Brobecker
2013-01-09 10:53 ` [RFA/commit+doco 2/2] Windows x64 SEH unwinder Joel Brobecker
2013-01-09 15:52 ` Pedro Alves
2013-01-09 16:28 ` Tristan Gingold
2013-01-09 17:10 ` Pedro Alves
2013-01-09 20:07 ` Tristan Gingold
2013-01-10 16:24 ` Pedro Alves
2013-07-08 10:55 ` [RFA] Windows x64 SEH unwinder (v2) Tristan Gingold
2013-07-26 15:22 ` Pedro Alves
2013-08-19 13:59 ` Tristan Gingold
2013-08-19 14:13 ` Pedro Alves
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=5215E662.5020902@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.com \
--cc=roland.schwingel@onevision.de \
/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