public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug cli/22454] logging sometimes prints prompt Date: Wed, 29 Mar 2023 15:19:26 +0000 [thread overview] Message-ID: <bug-22454-4717-CWNQvxn7QV@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-22454-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=22454 Tom de Vries <vries at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vries at gcc dot gnu.org --- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> --- I ran into this as well with gdb.ada/access_to_packed_array.exp, and a target board that defaults to "set editing off". This fixed it for me: ... diff --git a/gdb/event-top.c b/gdb/event-top.c index 53ddd515be7..e5838bafc33 100644 --- a/gdb/event-top.c +++ b/gdb/event-top.c @@ -447,8 +447,8 @@ display_gdb_prompt (const char *new_prompt) /* Don't use a _filtered function here. It causes the assumed character position to be off, since the newline we read from the user is not accounted for. */ - printf_unfiltered ("%s", actual_gdb_prompt.c_str ()); - gdb_flush (gdb_stdout); + printf ("%s", actual_gdb_prompt.c_str ()); + fflush (stdout); } } ... which I suppose mimics what readline would otherwise do. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-29 15:19 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 2023-03-29 15:19 ` vries at gcc dot gnu.org [this message] 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-CWNQvxn7QV@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: linkBe 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).