public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug ada/28180] FAIL: gdb.ada/interface.exp: print s (timeout)
Date: Tue, 17 Aug 2021 20:08:16 +0000	[thread overview]
Message-ID: <bug-28180-4717-4k1V7ZXuhg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28180-4717@http.sourceware.org/bugzilla/>

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

--- Comment #15 from Tom Tromey <tromey at sourceware dot org> ---
Daniel's suggestion is basically Tom's patch in comment #4,
so I think we ought to go with that.

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

  parent reply	other threads:[~2021-08-17 20:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02 22:32 [Bug ada/28180] New: " vries at gcc dot gnu.org
2021-08-02 22:32 ` [Bug ada/28180] " vries at gcc dot gnu.org
2021-08-02 22:36 ` vries at gcc dot gnu.org
2021-08-03 21:03 ` tromey at sourceware dot org
2021-08-04 20:06 ` tromey at sourceware dot org
2021-08-05 10:11 ` vries at gcc dot gnu.org
2021-08-05 10:56 ` vries at gcc dot gnu.org
2021-08-05 13:03 ` vries at gcc dot gnu.org
2021-08-05 13:17 ` vries at gcc dot gnu.org
2021-08-05 15:04 ` vries at gcc dot gnu.org
2021-08-06 16:16 ` tromey at sourceware dot org
2021-08-08  8:35 ` vries at gcc dot gnu.org
2021-08-13 18:42 ` tromey at sourceware dot org
2021-08-13 18:53 ` tromey at sourceware dot org
2021-08-14 13:13 ` vries at gcc dot gnu.org
2021-08-14 14:36 ` vries at gcc dot gnu.org
2021-08-17 18:05 ` brobecker at gnat dot com
2021-08-17 20:08 ` tromey at sourceware dot org [this message]
2021-08-24 11:14 ` vries at gcc dot gnu.org
2021-10-05 11:18 ` vries at gcc dot gnu.org
2024-03-08  9:55 ` sam at gentoo 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-28180-4717-4k1V7ZXuhg@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).