public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org>,
	Joel Brobecker <brobecker@adacore.com>
Subject: Re: GDB 12 branching next weekend (2022-03-20 or 2022-03-21)?
Date: Fri, 18 Mar 2022 07:33:17 +0400	[thread overview]
Message-ID: <YjP9fWtu9/CHdt+N@adacore.com> (raw)
In-Reply-To: <87ee31tyk7.fsf@redhat.com>

> > 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
> >
> >         Backport request on GDB ml:
> >         https://sourceware.org/pipermail/gdb-patches/2022-March/186391.html
> >
> >         There was a suggestion that we use a more limited bug safer
> >         approach for GDB 12. I did not look at the patch, but if it
> >         helps make people more comfortable, this seems like a valid
> >         approach.
> 
> I've now pushed the more limited work around for this issue, which
> should be good enough for GDB 12 (unless anyone wants to argue in favour
> of the full fix making the release).
> 
> >
> >   * [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
> >
> >         Let's push the patch ;-).
> 
> This is now pushed.

Awesome. Thanks for the patches, and the update, Andrew!

-- 
Joel

      reply	other threads:[~2022-03-18  3:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-13  4:55 Joel Brobecker
2022-03-16 20:47 ` Andrew Burgess
2022-03-18  3:33   ` Joel Brobecker [this message]

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=YjP9fWtu9/CHdt+N@adacore.com \
    --to=brobecker@adacore.com \
    --cc=aburgess@redhat.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).