Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Nitish Kumar Mishra <mishra.nitish.88@gmail.com>, gdb@sourceware.org
Subject: Re: Issue with Latest GDB on AIX with GCC-6.12
Date: Wed, 25 Jan 2017 14:38:00 -0000	[thread overview]
Message-ID: <20170125143729.GU28060@E107787-LIN> (raw)
In-Reply-To: <12a05075-3783-9d3f-1d3c-81931ea91f47@redhat.com>

On 17-01-25 13:52:49, Pedro Alves wrote:
> 
> So I'm out of ideas.  It looks like a toolchain/runtime bug
> to me.
> 

Hi Pedro,
GDB on AIX (at least gcc119) is broken since Nov 2016 at least.
https://sourceware.org/ml/gdb/2016-11/msg00023.html

I tried to debug libgcc on exception unwinding (in assembly!).  I
have a vague memory that unwinder stops unwinding after one or two
frames.  I suspect either gcc generate wrong .eh_frame or libgcc
is buggy.  That is where I stopped.

-- 
Yao (齐尧)


  parent reply	other threads:[~2017-01-25 14:38 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2017-01-25 14:44       ` Pedro Alves
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
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

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=20170125143729.GU28060@E107787-LIN \
    --to=qiyaoltc@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=mishra.nitish.88@gmail.com \
    --cc=palves@redhat.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