From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org,
Sergio Durigan Junior <sergiodj@redhat.com>,
antoine.tremblay@ericsson.com, mishra.nitish.88@gmail.com
Subject: Re: GDB 8.0 release / imminent branching? (2017-04-10)
Date: Tue, 11 Apr 2017 14:21:00 -0000 [thread overview]
Message-ID: <m3efwz9g9k.fsf@oc1027705133.ibm.com> (raw)
In-Reply-To: <20170411011802.s24zz4pygnt2qoyg@adacore.com> (Joel Brobecker's message of "Mon, 10 Apr 2017 18:18:02 -0700")
On Mon, Apr 10 2017, Joel Brobecker wrote:
> We have two 8.0 pending PRs:
>
> * server/21169 GDBServer on ARM can crash the inferior while single stepping
>
> Antoine indicated that he's working on it, and his expected
> completion date isn't all that far away. Still on track for
> that, Antoine?
>
> * build/21187 Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform
>
> For this one, I think the feedback so far is a question about
> the fact that this is only a work around. Parallel to that,
> did I see a thread where people are discussing a real fix
> for the exception handling issue?
>
> So, perhaps we might not need the GDB patch after all?
> Is there a version of GCC capable of compiling GDB 8.x
> on AiX?
Maybe not be relevant for answering your question, but the issue doesn't
seem to be restricted to AIX. It occurs on Windows with mingw as well,
see gdb/21078 ("gdb compiled with mingw32 crashes on Windows7 when
entering any invalid command").
In addition to those PRs, It'd be great to get some of the DWARF piece
handling fixes in GDB 8.0, particularly the fix for gdb/21226. There's
a patch set available that "just" needs review:
https://sourceware.org/ml/gdb-patches/2017-04/msg00177.html
Also, I wonder who can look at exp/21162 ("GDB internal error with
unbounded array typecast expression"). It's a regression introduced
when adding variable length array support in April 2014. The author,
Sanimir Agovic, doesn't seem to be active in GDB development any more?
The patch was reviewed by Joel Brobecker, though... ;-)
And last week a GDB internal error in value.c was reported as gdb/21356.
I haven't checked whether that is a regression or not.
--
Andreas
next prev parent reply other threads:[~2017-04-11 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 1:18 Joel Brobecker
2017-04-11 7:47 ` Yao Qi
2017-04-11 14:21 ` Andreas Arnez [this message]
2017-04-11 15:39 ` Yao Qi
2017-04-12 15:38 ` Joel Brobecker
2017-04-11 15:41 ` Eli Zaretskii
2017-04-12 14:18 ` Joel Brobecker
2017-04-11 19:00 ` Antoine Tremblay
2017-04-12 5:27 ` Sergio Durigan Junior
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=m3efwz9g9k.fsf@oc1027705133.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=antoine.tremblay@ericsson.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mishra.nitish.88@gmail.com \
--cc=sergiodj@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