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 testsuite/29659] [gdb/testsuite] local-remote-host timeouts with bracketed-paste
Date: Fri, 07 Oct 2022 10:06:44 +0000	[thread overview]
Message-ID: <bug-29659-4717-nFoT3lokJQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29659-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29659

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
> With test-case gdb.server/connect-with-no-symbol-file.exp and host board
> local-remote-host-notty, I have:
> ...
> Type "apropos word" to search for commands related to "word".^M
> (gdb) set height 0^M
> (gdb) set width 0^M
> (gdb) disconnect^M
> You can't do that when your target is `None'^M
> ...

Hmm, occasionally I also run into:
...
Type "apropos word" to search for commands related to "word".^M
(gdb) set height 0^M
(gdb) set width 0^M
(gdb) disconnect^M
You can't do that when your target is `None'(gdb) ^M
FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=: action=permission:
setup: disconnect (timeout)
...
So, a "\n" seems to have gone missing.

Hmm, that seems to be fixed by:
...
diff --git a/gdb/exceptions.c b/gdb/exceptions.c
index fdb65b3dc4b..fa962964042 100644
--- a/gdb/exceptions.c
+++ b/gdb/exceptions.c
@@ -85,6 +85,7 @@ print_exception (struct ui_file *file, const struct gdb_exc
eption &e)
        }
     }                                      
   gdb_printf (file, "\n");
+  print_flush ();

   /* Now append the annotation.  */
   switch (e.reason)
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-10-07 10:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07  8:20 [Bug testsuite/29659] New: " vries at gcc dot gnu.org
2022-10-07  8:22 ` [Bug testsuite/29659] " vries at gcc dot gnu.org
2022-10-07  8:35 ` vries at gcc dot gnu.org
2022-10-07 10:06 ` vries at gcc dot gnu.org [this message]
2022-10-07 10:09 ` vries at gcc dot gnu.org
2022-10-08 17:23 ` tromey at sourceware dot org
2022-10-09  8:56 ` vries at gcc dot gnu.org
2022-10-10 16:13 ` tromey at sourceware dot org
2022-10-12  4:04 ` vries at gcc dot gnu.org
2022-10-17 13:02 ` vries at gcc dot gnu.org
2022-10-17 13:05 ` vries at gcc dot gnu.org
2022-10-17 13:06 ` vries at gcc dot gnu.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-29659-4717-nFoT3lokJQ@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).