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 preparation -- 2022-02-20 update
Date: Tue, 22 Feb 2022 05:50:50 +0400	[thread overview]
Message-ID: <YhRBehiyNHJGeGff@adacore.com> (raw)
In-Reply-To: <87h78sct7n.fsf@redhat.com>

Hi Andrew,

> > Other Ongoing Items:
> > --------------------
> >
> >   * [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.
> >
> >         Andrew posted progress on the PR. Currently coordinating
> >         with the readline maintainers (seems to be progressing well)...
> 
> My ideal solution here would be to have an official readline patch
> committed upstream, which we can then backport, along with a GDB patch,
> to fix this issue.
> 
> If it looks like a readline patch isn't going to appear any time soon,
> then I'll post something later this week which we can consider - maybe
> just including it in the GDB 12 branch, and then wait for an official
> readline patch to include in master.
> 
> But I think we can give upstream readline a few more days to see how
> that plays out.

Agreed. I don't think we're in a rush, since we are still a month
away from our target branching date.

-- 
Joel

  reply	other threads:[~2022-02-22  1:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-20 11:43 Joel Brobecker
2022-02-21 12:14 ` Andrew Burgess
2022-02-22  1:50   ` Joel Brobecker [this message]
2022-02-22 19:34 ` 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=YhRBehiyNHJGeGff@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).