From: John Baldwin <jhb@FreeBSD.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: starting the GDB 14 release process
Date: Thu, 27 Jul 2023 08:43:16 -0700 [thread overview]
Message-ID: <53a12c46-cf2a-c6df-fcde-656a7454aa28@FreeBSD.org> (raw)
In-Reply-To: <ZMHaHfTGZb/PpaDx@adacore.com>
On 7/26/23 7:44 PM, Joel Brobecker wrote:
> Hi John,
>
>> 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.
>
> Thanks for the heads up. What's the ETA for those patches, do you think?
In theory the second series I can push without approval since it is all
FreeBSD-specific and earlier revisions have had some review. I'm happy
to still get more review, but given some of the cases it fixes (e.g.
being able to debug usefully across a fork when staying attached to
both processes), I'd rather have an imperfect version of it in 14 than
wait to get it completely perfect.
For the XSAVE series, that one is getting useful review feedback from Simon,
and I do have a workaround for the one issue Keith encountered while testing
it. I do need some resolution for which type of workaround we want to use
though.
--
John Baldwin
next prev parent reply other threads:[~2023-07-27 15:43 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
2023-07-27 2:44 ` Joel Brobecker
2023-07-27 15:43 ` John Baldwin [this message]
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=53a12c46-cf2a-c6df-fcde-656a7454aa28@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).