Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: Pedro Alves <pedro@palves.net>
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: Mon, 13 Feb 2017 15:02:00 -0000	[thread overview]
Message-ID: <CAGWvnymCQL62BDZCX_ftf11sbqxrhPgbKoYZ4iQkFW8-2Tk-Ag@mail.gmail.com> (raw)
In-Reply-To: <5967c781-4f67-06f2-db34-f4cb3818d603@palves.net>

On Sun, Feb 12, 2017 at 6:52 PM, Pedro Alves <pedro@palves.net> wrote:
> On 02/12/2017 09:05 PM, David Edelsohn wrote:
>
>> Investigating the exception handling problem with another non-IBM AIX
>> developer, the problem appears to be that statically linking libgcc
>> and libstdc++ create two, separate and distinct copies of the unwind
>> tables.  These tables are not merged and the unwinder cannot find the
>> EH catcher.  It's not immediately clear why this worked in GCC 4.8 and
>> not in GCC 4.9 and later.
>>
>> GDB with exception handling should work if libgcc and libstdc++ are
>> linked as shared libraries.  The linking error with GCC 6.1 is cockpit
>> error.
>>
>> Can we disable -static-libgcc and -static-libstdc++ for AIX?
>
> Works for me.  Those are added by the top level configure.  They were
> originally added for gcc, we just inherited it.  Ideally adding
> those would be controllable with a configure option, IMO.

We shouldn't disable static-libgcc and static-libstdc++ for GCC.  And
static would be better.  But linking GDB dynamically could be helpful
as an interim work-around.

Thanks, David


  reply	other threads:[~2017-02-13 15:02 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
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 [this message]
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=CAGWvnymCQL62BDZCX_ftf11sbqxrhPgbKoYZ4iQkFW8-2Tk-Ag@mail.gmail.com \
    --to=dje.gcc@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=mishra.nitish.88@gmail.com \
    --cc=pedro@palves.net \
    --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