From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCHv2 0/3] Fix GDB prompt corruption issue
Date: Mon, 14 Mar 2022 10:23:40 +0000 [thread overview]
Message-ID: <cover.1647253263.git.aburgess@redhat.com> (raw)
In-Reply-To: <cover.1646665813.git.aburgess@redhat.com>
Here's a revised plan for PR gdb/28833.
I've split the series into 3 patches. The first is (I claim) the
smallest patch that mitigates against the problem reported in
gdb/28833, but isn't a complete fix. This first patch is what I'd
like to push soon (before GDB 12 branches).
Patches 2 and 3 are the full fix. These I'd like to push after GDB 12
branches.
Thoughts?
Thanks,
Andrew
---
Andrew Burgess (3):
gdb: work around prompt corruption caused by bracketed-paste-mode
readline: back-port changes needed to properly detect EOF
gdb: handle bracketed-paste-mode and EOF correctly
gdb/event-top.c | 64 ++++++++++++++++++++-
gdb/event-top.h | 6 ++
gdb/testsuite/gdb.base/eof-exit.exp | 88 +++++++++++++++++++++++++++++
gdb/testsuite/lib/gdb.exp | 9 +++
gdb/top.c | 1 +
readline/readline/callback.c | 8 ++-
readline/readline/doc/rltech.texi | 11 ++++
readline/readline/readline.c | 19 ++++---
readline/readline/readline.h | 8 ++-
readline/readline/rlprivate.h | 1 -
readline/readline/rltty.c | 4 +-
11 files changed, 206 insertions(+), 13 deletions(-)
create mode 100644 gdb/testsuite/gdb.base/eof-exit.exp
--
2.25.4
next prev parent reply other threads:[~2022-03-14 10:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 15:13 [PATCH 0/2] " Andrew Burgess
2022-03-07 15:13 ` [PATCH 1/2] readline: back-port changes needed to properly detect EOF Andrew Burgess
2022-03-09 17:45 ` Tom Tromey
2022-03-07 15:13 ` [PATCH 2/2] gdb: handle bracketed-paste-mode and ctrl-d correctly Andrew Burgess
2022-03-07 17:10 ` Eli Zaretskii
2022-03-08 9:45 ` Andrew Burgess
2022-03-08 12:10 ` Eli Zaretskii
2022-03-14 10:23 ` Andrew Burgess [this message]
2022-03-14 10:23 ` [PATCHv2 1/3] gdb: work around prompt corruption caused by bracketed-paste-mode Andrew Burgess
2022-03-16 17:31 ` Tom Tromey
2022-03-16 20:45 ` Andrew Burgess
2022-03-17 8:22 ` Aktemur, Tankut Baris
2022-03-25 18:32 ` Simon Marchi
2022-03-26 14:02 ` Andrew Burgess
2022-03-27 0:59 ` Simon Marchi
2022-03-14 10:23 ` [PATCHv2 2/3] readline: back-port changes needed to properly detect EOF Andrew Burgess
2022-03-14 10:23 ` [PATCHv2 3/3] gdb: handle bracketed-paste-mode and EOF correctly Andrew Burgess
2022-03-21 15:58 ` [PATCHv3 0/2] Fix GDB prompt corruption issue Andrew Burgess
2022-03-21 15:58 ` [PATCHv3 1/2] readline: back-port changes needed to properly detect EOF Andrew Burgess
2022-03-21 15:58 ` [PATCHv3 2/2] gdb: handle bracketed-paste-mode and EOF correctly Andrew Burgess
2022-03-29 14:26 ` [PATCHv4 0/3] Fix GDB prompt corruption issue Andrew Burgess
2022-03-29 14:26 ` [PATCHv4 1/3] gdb: improved EOF handling when using readline 7 Andrew Burgess
2022-03-29 14:26 ` [PATCHv4 2/3] readline: back-port changes needed to properly detect EOF Andrew Burgess
2022-03-29 14:26 ` [PATCHv4 3/3] gdb: handle bracketed-paste-mode and EOF correctly Andrew Burgess
2022-04-21 16:49 ` [PATCHv4 0/3] Fix GDB prompt corruption issue Andrew Burgess
2022-04-22 17:52 ` Andrew Burgess
2022-04-26 14:27 ` Andrew Burgess
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=cover.1647253263.git.aburgess@redhat.com \
--to=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).