public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "aburgess at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/29706] [gdb, readline 8.2] FAIL: gdb.base/eof-exit.exp: with non-dump terminal: with bracketed-paste-mode on: close GDB with eof (missed the prompt)
Date: Wed, 26 Oct 2022 16:24:07 +0000 [thread overview]
Message-ID: <bug-29706-4717-SBngUkr3cM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29706-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29706
--- Comment #4 from Andrew Burgess <aburgess at redhat dot com> ---
I've also tried to reproduce this without success. I did wonder if it was
possible that an update to libreadline might trigger this behaviour, with GDB
built against readline 8.1, then an update to readline 8.2 being performed
without rebuilding GDB.
It was in the 8.1 -> 8.2 readline update that the bugs related to how the
'quit' is printed were fixed.
That said, I don't have a solid story for what might be triggering the weird
behaviour - the readline update is just an idea. I have an opensuse VM, but I
can't figure out how to downgrade readline to 8.1 in order to test the
theory...
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-10-26 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 8:50 [Bug testsuite/29706] New: " vries at gcc dot gnu.org
2022-10-20 8:50 ` [Bug testsuite/29706] " vries at gcc dot gnu.org
2022-10-20 9:23 ` vries at gcc dot gnu.org
2022-10-20 9:25 ` vries at gcc dot gnu.org
2022-10-24 8:00 ` vries at gcc dot gnu.org
2022-10-26 16:24 ` aburgess at redhat dot com [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=bug-29706-4717-SBngUkr3cM@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).