From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: GDB 12 preparation -- 2022-03-06 update
Date: Sun, 6 Mar 2022 14:15:12 +0400 [thread overview]
Message-ID: <YiSJsFO+XMiDkUyN@adacore.com> (raw)
Hi everyone,
We are making very good progress, it seems, on the two issues
we have identified for GDB 12, so if things continue this way,
we might be on track to create our first pre-release around
the time we were targetting, which is March 20-25 (repeated
at the end of every message, just for the record)!
There has also been ...
https://sourceware.org/bugzilla/show_bug.cgi?id=28616
... where I wasn't sure why it was marked GDB 12, and have been
trying to reach out to the person who created the PR. I've tried
a different email which I think will work. Given that I'm not
seeing progress on this PR either, I'm hoping this one isn't
going to be deemed critical (it does seem to happen in unusual
circumstances, but workarounds once hist are unclear at the moment).
That's it for this week. Let's see where we're at at the end
of next week :).
---
Fixed Since the Previous Update:
--------------------------------
<none>
Added Since the Last Update:
----------------------------
<none>
Other Ongoing Items:
--------------------
* TBC: [BarisA/AndrewB] <PR cli/28833>
Ctrl-D distorts GDB prompt
https://sourceware.org/bugzilla/show_bug.cgi?id=28833
Baris requested that we consider the bug above, which seems
to be a GDB 11 regression for Baris.
IIUC, Andrew fixed the issue in upstream's readline, and
now we just need to backport it.
https://lists.gnu.org/archive/html/bug-readline/2022-03/msg00005.html
* [AndrewB] create GDB/MI commands using python
Explicit request to include in GDB 12; accepted as the patches
were sent prior to the start of the GDB 12 release process.
Latest version (v5) pasted by Andrew, and approved by Tom:
https://sourceware.org/pipermail/gdb-patches/2022-February/186176.html
Reminder: Tentative Schedule:
-----------------------------
- GDB 12 branching: ~Mar 20-25;
- GDB 12.1 release 2 weeks later, so early Apr.
--
Joel
next reply other threads:[~2022-03-06 10:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 10:15 Joel Brobecker [this message]
2022-03-07 8:50 ` Luis Machado
2022-03-07 11:45 ` Joel Brobecker
2022-03-07 15:01 ` Tom Tromey
2022-03-07 16:14 ` Joel Brobecker
2022-03-07 17:43 ` Tom Tromey
2022-03-07 15:15 ` Andrew Burgess
2022-03-07 16:14 ` 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=YiSJsFO+XMiDkUyN@adacore.com \
--to=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).