From: Joel Brobecker <brobecker@adacore.com>
To: Simon Marchi <simark@simark.ca>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: GDB 13 release -- 2022-11-19 update
Date: Tue, 22 Nov 2022 19:31:24 +0400 [thread overview]
Message-ID: <Y3zrTOtjkpzl0eP/@adacore.com> (raw)
In-Reply-To: <95e11efa-8fbc-0de9-c27b-669235d496fa@simark.ca>
Hi Simon,
On Tue, Nov 22, 2022 at 10:10:53AM -0500, Simon Marchi wrote:
> On 11/19/22 07:42, Joel Brobecker via Gdb-patches wrote:
> > Hi everyone,
> >
> > Here is an update since last time. It feels like we git a significant
> > influx of new PRs added to the list. Fortunately, have have patches
> > for many of them.
> >
> > Additionally, Tom told me last Wed that he's send his last patches
> > for the DWARF reader, so IIUC, if there are more issues that haven't
> > been addressed yet, please report them!
>
> Hi Joel,
>
> I think this series would be nice to have in GDB 13:
>
> Fix some commit_resumed_state assertion failures (PR 28275)
> https://inbox.sourceware.org/gdb-patches/20221121171213.1414366-1-simon.marchi@polymtl.ca/T/#m20705093bf5d0feea4f0c54691c61f320e1d162b
Sounds good, Simon. I've tagged the PR with a 13.1 milestone.
> Also, do you think there will be a GDB 12.2? Even if there isn't, I
> would probably push the patches to the GDB 12 branch anyway, in case
> someone wants to build it from the branch.
There weren't enough changes in the gdb-12-branch to warrant
a 12.2 release. We can of course rediscuss, but feel free to
backport the change to the gdb-12-branch regardless. We've done
so before, after .2 releases as well, for the exact reason
you mentioned.
--
Joel
next prev parent reply other threads:[~2022-11-22 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 12:42 Joel Brobecker
2022-11-19 14:55 ` Philippe Waroquiers
2022-11-20 14:55 ` Rainer Orth
2022-11-22 15:10 ` Simon Marchi
2022-11-22 15:31 ` Joel Brobecker [this message]
2022-11-22 15:34 ` Simon Marchi
2022-11-23 15:54 ` Philippe Waroquiers
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=Y3zrTOtjkpzl0eP/@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).