From: John Baldwin <jhb@FreeBSD.org>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: starting the GDB 14 release process
Date: Wed, 26 Jul 2023 11:31:47 -0700 [thread overview]
Message-ID: <11f64d57-3985-86a7-77fa-04fcae5151e8@FreeBSD.org> (raw)
In-Reply-To: <ZKWK1M+trL1709Ia@adacore.com>
On 7/5/23 8:23 AM, Joel Brobecker via Gdb-patches wrote:
> Hi everyone,
>
> Time to start the process for the next major release (GDB 14.1).
>
> The first order of business for this is to start collecting the list
> of issues that we think should be blocking for that release (and among
> those, which ones should block the creation of the branch).
>
> Are there issues you think should be blocking for 14.1? And if there
> is a Bugzilla PR already, can you provide their PR number?
I don't have PRs, but I have two series open that I'd like to be in 14.1:
- Handle variable XSAVE layouts
- Fixes for multiprocess for FreeBSD's native target
This latter one does include a fix for PR 21497
I could open a PR for the former for the bug where you can't examine
XSAVE registers (like AVX) from core dumps generated on modern AMD
processors.
--
John Baldwin
next prev parent reply other threads:[~2023-07-26 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 15:23 Joel Brobecker
2023-07-24 8:23 ` Luis Machado
2023-07-26 15:26 ` Joel Brobecker
2023-07-27 12:00 ` Luis Machado
2023-07-26 15:36 ` Tom Tromey
2023-07-26 15:44 ` Joel Brobecker
2023-07-26 18:31 ` John Baldwin [this message]
2023-07-27 2:44 ` Joel Brobecker
2023-07-27 15:43 ` John Baldwin
2023-09-06 2:19 ` John Baldwin
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=11f64d57-3985-86a7-77fa-04fcae5151e8@FreeBSD.org \
--to=jhb@freebsd.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).