From: Simon Marchi <simark@simark.ca>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: GDB 8.3 release update (2019-03-25)
Date: Mon, 25 Mar 2019 22:29:00 -0000 [thread overview]
Message-ID: <8f3455a2-4e77-0e0b-85b0-323bdfbb1269@simark.ca> (raw)
In-Reply-To: <20190325204307.GA21459@adacore.com>
On 2019-03-25 4:43 p.m., Joel Brobecker wrote:
> Hello,
>
> Sorry for the fairly long delay since the last "update" (aka
> pre-release). I was busy traveling, and I was also seeing
> a fair amount of activity on all the issues being discovered.
>
> To me, it looks like all issues reported for that version
> have been fixed?
>
> In terms of bugzilla, there are no open bugs targetting 8.3
> at the moment, so we are good on this end too.
>
> If we can confirm there aren't any issues we know of that we want
> to fix for 8.3, I could create the release, say, this weekend, or
> early next week.
>
There is this that I would consider quite blocking;
https://sourceware.org/ml/gdb-patches/2019-03/msg00517.html
I haven't checked if the bug appears in 8.3, but I would bet that it
does, since the patch that caused it was pushed to master and the 8.3
branch.
In any case, it should be fixed in the coming days. I will still put an
entry in the release page on the wiki.
Simon
next prev parent reply other threads:[~2019-03-25 22:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 20:43 Joel Brobecker
2019-03-25 20:51 ` Eli Zaretskii
2019-03-26 20:40 ` Joel Brobecker
2019-03-26 20:46 ` Eli Zaretskii
2019-03-25 22:26 ` Sergio Durigan Junior
2019-03-26 20:48 ` Joel Brobecker
2019-03-26 21:31 ` Sergio Durigan Junior
2019-03-26 22:46 ` Joel Brobecker
2019-03-25 22:29 ` Simon Marchi [this message]
2019-03-26 21:15 ` Pedro Franco de Carvalho
2019-03-26 22:21 ` Joel Brobecker
2019-03-27 13:30 ` Tom Tromey
2019-03-27 19:47 ` Pedro Franco de Carvalho
2019-03-27 19:51 ` Pedro Alves
2019-03-28 17:36 ` Joel Brobecker
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=8f3455a2-4e77-0e0b-85b0-323bdfbb1269@simark.ca \
--to=simark@simark.ca \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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