public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "sandra at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/22454] logging sometimes prints prompt
Date: Fri, 26 Jun 2020 22:17:25 +0000 [thread overview]
Message-ID: <bug-22454-4717-HEGWtkECfd@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22454-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22454
sandra at codesourcery dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandra at codesourcery dot com
--- Comment #2 from sandra at codesourcery dot com ---
I'm seeing these FAILs in testing on a remote host that can't support readline
because stdin isn't a tty:
FAIL: gdb.base/ui-redirect.exp: redirect: set logging on (timeout)
FAIL: gdb.base/ui-redirect.exp: redirect: save breakpoints cmds.txt (timeout)
FAIL: gdb.base/ui-redirect.exp: redirect: userdefined (timeout)
They're timing out because the prompt is appearing in the log file instead of
stdout, causing gdb_test to wait indefinitely for output that never arrives.
Surely this is a bug somewhere else and not an inherent dependency on readline
features?
--
You are receiving this mail because:
You are on the CC list for the bug.
next parent reply other threads:[~2020-06-26 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-22454-4717@http.sourceware.org/bugzilla/>
2020-06-26 22:17 ` sandra at codesourcery dot com [this message]
2023-03-29 15:19 ` vries at gcc dot gnu.org
2023-03-29 16:53 ` vries at gcc dot gnu.org
2024-05-10 18:16 ` tromey at sourceware dot org
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-22454-4717-HEGWtkECfd@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).