Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: Nitish Kumar Mishra <mishra.nitish.88@gmail.com>
Cc: Pedro Alves <palves@redhat.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: Fri, 10 Feb 2017 15:52:00 -0000	[thread overview]
Message-ID: <CAGWvnykPRFF0LW2dG5sVTx5w7sp0u-6b-iXshDzGXKUfWJbKDQ@mail.gmail.com> (raw)
In-Reply-To: <CACC+hkj42Sz3pcOV7yRMZTboiCd8YFOwGug6NEgeEtWyyOC4gg@mail.gmail.com>

On Fri, Feb 10, 2017 at 2:22 AM, Nitish Kumar Mishra
<mishra.nitish.88@gmail.com> wrote:
> Hi All,
>
>> 3. GDB with GCC-6.1, 64 bit mode, with static options : NOT WORKING
>> 4. GDB with GCC-6.1, 64 bit mode, without static options : COMPILATION ERROR.
>>
>> P.S.: Static options means: -static-libstdc++ -static-libgcc
>
>>What is the compilation error?
> With GCC-6.1, 64 bit mode, WITHOUT static option, below is the output of the
> compilation error:
>
> ld: 0711-317 ERROR: Undefined symbol: ._Unwind_Resume
> ld: 0711-317 ERROR: Undefined symbol: .__cxa_atexit
> ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information.
> collect2: error: ld returned 8 exit status
>
>
>> Does GCC 4.8.5 and GCC 6.1 fail in the same manner?  Neither catch the
> exception?
> Yes, by NOT WORKING, I meant, niether catching the exception and process is
> getting terminated.

Who built GCC 6.1 for you?  Is this an IBM build or Bull Freeware?

The version of GCC that you are using was built incorrectly.  There
have been problems in the past with some of the pre-built binaries
containing libraries with recently added symbols not correctly
exported.

There seems to be a problem with exception handling and -static-libgcc
in recent versions of GCC on AIX.  I don't know what you have been
testing and why you were not able to triage this.

Thanks, David


  reply	other threads:[~2017-02-10 15:52 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 [this message]
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=CAGWvnykPRFF0LW2dG5sVTx5w7sp0u-6b-iXshDzGXKUfWJbKDQ@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