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 dap/31275] [gdb/dap, gdb.dap/pause.exp] ERROR: timeout reading json header
Date: Tue, 23 Jan 2024 16:42:17 +0000	[thread overview]
Message-ID: <bug-31275-4717-0OHqZhqI68@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31275-4717@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
I wonder what's going on here:

"During handling of the above exception, another exception occurred:\n"

What I think should happen is that the work on the main
thread should be interrupted by a KeyboardInterrupt; then
this should be forwarded to the server thread (via the result queue).
Then finally the server thread should post the "cancelled" response.

From the stack trace this seems to be partly correct but,
for some reason, we get this "another exception" error -- but
without details really.

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

  parent reply	other threads:[~2024-01-23 16:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 19:05 [Bug dap/31275] New: " vries at gcc dot gnu.org
2024-01-22 19:07 ` [Bug dap/31275] " vries at gcc dot gnu.org
2024-01-22 20:32 ` tromey at sourceware dot org
2024-01-23 11:55 ` vries at gcc dot gnu.org
2024-01-23 16:42 ` tromey at sourceware dot org [this message]
2024-02-08 16:06 ` vries at gcc dot gnu.org
2024-02-08 17:00 ` vries at gcc dot gnu.org
2024-02-12 18:59 ` tromey at sourceware dot org
2024-02-19 15:21 ` vries at gcc dot gnu.org
2024-02-23 16:52 ` vries at gcc dot gnu.org
2024-02-29 20:29 ` cvs-commit at gcc dot gnu.org
2024-02-29 20:30 ` 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-31275-4717-0OHqZhqI68@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).