From: David Edelsohn <dje.gcc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Nitish Kumar Mishra <mishra.nitish.88@gmail.com>,
"gdb@sourceware.org" <gdb@sourceware.org>,
Yao Qi <qiyaoltc@gmail.com>
Subject: Re: Issue with Latest GDB on AIX with GCC-6.12
Date: Tue, 07 Feb 2017 14:16:00 -0000 [thread overview]
Message-ID: <CAGWvnykDzxS4uZfEgZOpUyPnHMaL_-jy4dD9oLcCnjgiK30bsg@mail.gmail.com> (raw)
In-Reply-To: <57147db4-83c3-2a8f-0c74-0efc6a94e9f5@redhat.com>
On Tue, Feb 7, 2017 at 8:56 AM, Pedro Alves <palves@redhat.com> wrote:
> On 02/07/2017 01:44 PM, David Edelsohn wrote:
>> On Tue, Feb 7, 2017 at 5:30 AM, Pedro Alves <palves@redhat.com> wrote:
>>
>>> Speaking of compilers, we know that building gdb with gcc 4.8.5
>>> doesn't run into this. Do we know that changed? Did, for example,
>>> AIX switch from sjlj to dwarf-based exceptions between gcc 4.8.5
>>> and 6.1? Might also be useful to try to build gdb with current
>>> gcc trunk / gcc 7.
>>
>> I cannot tell if some have reported that GCC 4.8.5 works correctly or not.
>
> The OP said it works fine on GCC 4.8.5 here:
>
> https://sourceware.org/ml/gdb/2017-01/msg00044.html
Yes, but I thought that there was a later comment that GCC 4.8 also
showed problems.
There was a change in the encoding of data for AIX, but not a change
to the basic EH frames or handlers. AIX did not change EH mechanisms
and never used SJLJ -- at least not for a very long time.
One test is to use shared libraries to link GDB.
Another possible contribution is the AIX address space. There have
been reports in the past of EH frames not sorted correctly and libgcc
EH not finding exception handlers because it terminated the search
early.
Thanks, David
next prev parent reply other threads:[~2017-02-07 14:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 23:56 David Edelsohn
2017-01-29 1:11 ` David Edelsohn
2017-01-31 13:09 ` Pedro Alves
2017-02-07 8:05 ` Nitish Kumar Mishra
2017-02-07 10:30 ` Pedro Alves
2017-02-07 13:44 ` David Edelsohn
2017-02-07 13:57 ` Pedro Alves
2017-02-07 14:16 ` David Edelsohn [this message]
2017-02-08 6:16 ` Nitish Kumar Mishra
2017-02-08 7:04 ` Nitish Kumar Mishra
2017-02-08 12:06 ` Pedro Alves
2017-02-08 13:32 ` David Edelsohn
2017-02-09 4:51 ` Nitish Kumar Mishra
2017-02-09 12:05 ` Nitish Kumar Mishra
2017-02-09 12:15 ` Nitish Kumar Mishra
2017-02-09 15:50 ` David Edelsohn
2017-02-10 7:22 ` Nitish Kumar Mishra
2017-02-10 15:52 ` David Edelsohn
2017-02-12 21:05 ` David Edelsohn
2017-02-12 23:52 ` Pedro Alves
2017-02-13 15:02 ` David Edelsohn
2017-02-13 15:19 ` Eli Zaretskii
2017-02-13 15:38 ` Nitish Kumar Mishra
2017-02-20 11:22 ` Nitish Kumar Mishra
2017-02-20 11:25 ` Nitish Kumar Mishra
2017-02-20 11:37 ` Nitish Kumar Mishra
2017-02-21 8:01 ` Nitish Kumar Mishra
2017-02-21 14:47 ` David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
2017-01-25 10:54 Nitish Kumar Mishra
2017-01-25 11:12 ` Pedro Alves
2017-01-25 13:52 ` Pedro Alves
2017-01-25 14:01 ` Pedro Alves
2017-01-25 14:38 ` Yao Qi
2017-01-25 14:44 ` 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=CAGWvnykDzxS4uZfEgZOpUyPnHMaL_-jy4dD9oLcCnjgiK30bsg@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=gdb@sourceware.org \
--cc=mishra.nitish.88@gmail.com \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.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