From: Simon Marchi <simon.marchi@polymtl.ca>
To: Andrew Burgess <aburgess@redhat.com>, Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCHv2 1/3] gdb: work around prompt corruption caused by bracketed-paste-mode
Date: Sat, 26 Mar 2022 20:59:32 -0400 [thread overview]
Message-ID: <c809adc6-7625-7269-02a4-392fc648b3b1@polymtl.ca> (raw)
In-Reply-To: <20220326140234.GU1212730@redhat.com>
> Thanks for the awesome steps to reproduce! This made it super easy to
> track down the problem.
>
> Basically the problem is that I only took readline 8+ into account
> when writing the test, this spin of ubuntu is on readline 7.
>
> The patch below changes the test FAIL into a KFAIL, which, if you were
> on readline 8 would be the best we could do.
>
> But given you're on readline 7, we should be able to do better,
> getting this to a PASS! But that will require changes to GDB itself.
>
> I'd like to propose that first we merge the patch below, this removes
> the FAIL, then next week I'll post a follow on patch for GDB that
> should get this test PASSing for readline 7.
>
> Thoughts?
Hi,
I am fine with the patch below. Unfortunately I am not up to speed on
what this issue with the prompt was, so I can't really help further.
Thanks for coming back with a "fix" quickly, that helps.
Just one nit in the commit message below.
> commit 7a0add556420e2ef814a6cd58501a832fdb1fb90
> Author: Andrew Burgess <aburgess@redhat.com>
> Date: Sat Mar 26 13:41:33 2022 +0000
>
> gdb/testsuite: fix test failure when building against readline v7
>
> The test added in the commit:
>
> commit a6b413d24ccc5d76179bab866834e11fd6fec294
> Date: Fri Mar 11 14:44:03 2022 +0000
>
> gdb: work around prompt corruption caused by bracketed-paste-mode
>
> Was not written with readline 7 in mind, only readline 8+. Between
> readline 7 and 8 the escape sequence used to disable bracketed paste
> mode changed, an additional '\r' character was added to the end. In
> fact, it was the addition of this '\r' character that triggered the
> issue for which the above commit is part of the solution.
>
> Anyway, the test tries to spot the case where the output from GDB is
> not perfect, but does have the above work around applied. However,
> the pattern in the test assume that the problematic '\r' will be
assume -> assumes
Simon
next prev parent reply other threads:[~2022-03-27 0:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 15:13 [PATCH 0/2] Fix GDB prompt corruption issue 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 ` [PATCHv2 0/3] Fix GDB prompt corruption issue Andrew Burgess
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 [this message]
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=c809adc6-7625-7269-02a4-392fc648b3b1@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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).