From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: start of the GDB 11 release cycle
Date: Mon, 10 May 2021 00:52:34 -0300 [thread overview]
Message-ID: <995340af-3cef-e322-0887-3a76bc6ad34d@linaro.org> (raw)
In-Reply-To: <20210510000448.GA4371@adacore.com>
Hi Joel,
On 5/9/21 9:04 PM, Joel Brobecker wrote:
> Hello,
>
> It's been about 6.5 months since we made the first GDB 10 release (10.1).
> So I propose we start the process of creating the GDB 11 release now.
>
> As of now, below are the issues that I'm aware of:
>
> * [Sergey with Simon as reviewer] <PR tdep/26633>
> Add Z80 CPU support
> https://sourceware.org/bugzilla/show_bug.cgi?id=26633
>
> Patch submitted at:
> https://sourceware.org/pipermail/gdb-patches/2020-September/172083.html
>
> * [AndrewB/Simon] <PR gdb/26819>
> Bug 26819 - RISC-V: internal-error: int finish_step_over(execution_control_state*): Assertion
> https://sourceware.org/bugzilla/show_bug.cgi?id=26819
>
> I think the situation has been improved thanks to a couple of
> patches, but the user still has some scenarios where the issue
> happens.
>
> * [Simon] <PR gdb/26868>
> Follow-up on x86-64 stub submission
> https://sourceware.org/bugzilla/show_bug.cgi?id=26868
>
> This is the submission in question:
> https://sourceware.org/pipermail/gdb-patches/2020-November/173182.html
>
> * [Simon/Kevin] <PR gdb/27526>
> Attaching to threaded process on glibc 2.33: libthread_db fails to initialize with "generic error"
>
> Patch v2 at:
> https://sourceware.org/pipermail/gdb-patches/2021-May/178485.html
>
> Are there other issues or last minute features we'd like to include
> before we branch and/or release?
For issues, I have a couple that I'd like to get fixed for AArch64 MTE
before GDB 11. I'll file those in bugzilla and will set the fields
accordingly.
In terms of features, I'd really like to get AArch64 MTE core file
support (dumping registers and memory tags) in before GDB 11. I don't
expect it to be a big change, but I'm still polishing the series so I
can submit it.
Given this step needs coordination with the kernel, there might be
delays here and there. Do you think that will be acceptable?
next prev parent reply other threads:[~2021-05-10 3:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 0:04 Joel Brobecker
2021-05-10 3:20 ` Mike Frysinger via Gdb-patches
2021-05-10 22:10 ` Joel Brobecker
2021-05-24 19:40 ` Joel Brobecker
2021-05-25 2:01 ` Mike Frysinger via Gdb-patches
2021-05-26 22:03 ` Joel Brobecker
2021-05-29 15:58 ` Mike Frysinger via Gdb-patches
2021-05-10 3:52 ` Luis Machado via Gdb-patches [this message]
2021-05-10 22:11 ` Joel Brobecker
2021-05-11 11:05 ` Luis Machado via Gdb-patches
2021-05-11 17:00 ` Joel Brobecker
2021-05-12 18:15 ` Luis Machado via Gdb-patches
2021-05-24 19:42 ` Joel Brobecker
2021-05-24 20:27 ` Luis Machado via Gdb-patches
2021-05-24 21:02 ` Joel Brobecker
2021-05-25 10:46 ` Luis Machado via Gdb-patches
2021-05-26 22:04 ` Joel Brobecker
2021-05-10 5:52 ` Bernd Edlinger
2021-05-10 15:10 ` Simon Marchi via Gdb-patches
2021-05-10 16:07 ` Andrew Burgess
2021-05-10 16:57 ` Simon Marchi via Gdb-patches
2021-05-10 22:12 ` Joel Brobecker
2021-05-11 12:45 ` Rainer Orth
2021-05-11 16:57 ` 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=995340af-3cef-e322-0887-3a76bc6ad34d@linaro.org \
--to=gdb-patches@sourceware.org \
--cc=brobecker@adacore.com \
--cc=luis.machado@linaro.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