From: Joel Brobecker <brobecker@adacore.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.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: Wed, 12 Apr 2017 14:18:00 -0000 [thread overview]
Message-ID: <20170412141836.yppwokhiqx6xjf47@adacore.com> (raw)
In-Reply-To: <m3efwz9g9k.fsf@oc1027705133.ibm.com>
Hi Andreas,
Thanks for pointing out more issues:
> 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").
Like Eli, I tried it, and it worked for me as well.
> 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
If we weren't already 4 weeks late, I might have given ourselves
an extra week to see if it got accepted, but we need to branch
soon and start stabilizing. Maybe the Global Maintainer reviewing
the changes will approve the changes for a backport, but it looks
a bit on the large side. Since it's before a .0, perhaps it'll be
considered safe enough for it.
> 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... ;-)
I wish I could tell you that I would look into this, but my schedule
for the next few weeks is completely packed...
> 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.
I reproduced the issue with 7.10, so not a regression. I'd guess
that this is a missing check_typedef somewhere, so might be fairly
simple to fix. I've added this item to the "maybe" list for 8.0
in the release's wiki page
(https://sourceware.org/gdb/wiki/GDB_8.0_Release).
--
Joel
next prev parent reply other threads:[~2017-04-12 14:18 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
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 [this message]
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=20170412141836.yppwokhiqx6xjf47@adacore.com \
--to=brobecker@adacore.com \
--cc=antoine.tremblay@ericsson.com \
--cc=arnez@linux.vnet.ibm.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