public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/28833] Ctrl-D distorts GDB prompt
Date: Fri, 22 Apr 2022 17:51:40 +0000	[thread overview]
Message-ID: <bug-28833-4717-sHKjBSoYML@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28833-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28833

--- Comment #15 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Burgess <aburgess@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=4fb7bc4b147fd30b781ea2dad533956d0362295a

commit 4fb7bc4b147fd30b781ea2dad533956d0362295a
Author: Andrew Burgess <aburgess@redhat.com>
Date:   Mon Mar 7 13:49:21 2022 +0000

    readline: back-port changes needed to properly detect EOF

    This commit is a partial back-port of this upstream readline commit:

      commit 002d31aa5f5929eb32d0e0e2e8b8d35d99e59961
      Author: Chet Ramey <chet.ramey@case.edu>
      Date:   Thu Mar 3 11:11:47 2022 -0500

          add rl_eof_found to public API; fix pointer aliasing problems  \
                with history-search-backward; fix a display problem with \
                runs of invisible characters at the end of a physical    \
                screen line

    I have only pulled in the parts of this commit that relate to the new
    rl_eof_found global, and the RL_STATE_EOF state flag.  These changes
    are needed in order to fix PR cli/28833, and are discussed in this
    thread to the bug-readline mailing list:

      https://lists.gnu.org/archive/html/bug-readline/2022-02/msg00021.html

    The above commit is not yet in any official readline release, but my
    hope is that now it has been merged into the readline tree it should
    be safe enough to back port this fix to GDB's tree.

    At some point in the future we will inevitably want to roll forward
    the version of readline that we maintain in the binutils-gdb
    repository.  When that day comes the changes in this commit can be
    replaced with the latest upstream readline code, as I have not changed
    the meaning of this code at all from what is in upstream readline.

    This commit alone does not fix the PR cli/28833 issue, for that see
    the next commit, which changes GDB itself.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=28833

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-04-22 17:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28  9:32 [Bug cli/28833] New: " tankut.baris.aktemur at intel dot com
2022-01-28  9:34 ` [Bug cli/28833] " tankut.baris.aktemur at intel dot com
2022-01-28  9:36 ` tankut.baris.aktemur at intel dot com
2022-01-28 16:07 ` tromey at sourceware dot org
2022-02-06 12:14 ` aburgess at redhat dot com
2022-02-07 10:28 ` tankut.baris.aktemur at intel dot com
2022-02-08 10:15 ` aburgess at redhat dot com
2022-02-14 12:14 ` blarsen at redhat dot com
2022-02-15 11:48 ` aburgess at redhat dot com
2022-02-15 12:34 ` schwab@linux-m68k.org
2022-02-15 14:01 ` aburgess at redhat dot com
2022-02-16 17:06 ` aburgess at redhat dot com
2022-02-17  7:01 ` tankut.baris.aktemur at intel dot com
2022-02-27 11:21 ` brobecker at gnat dot com
2022-03-06 10:05 ` brobecker at gnat dot com
2022-03-07 15:14 ` aburgess at redhat dot com
2022-03-16 20:44 ` cvs-commit at gcc dot gnu.org
2022-04-22 17:51 ` cvs-commit at gcc dot gnu.org
2022-04-22 17:51 ` cvs-commit at gcc dot gnu.org [this message]
2022-04-22 17:51 ` cvs-commit at gcc dot gnu.org
2022-04-22 17:53 ` aburgess at redhat dot com

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=bug-28833-4717-sHKjBSoYML@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).