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 gdb/30268] [gdb/dap] ERROR: timeout reading json header
Date: Thu, 23 Mar 2023 18:42:20 +0000 [thread overview]
Message-ID: <bug-30268-4717-2AzuHaS5Py@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30268-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30268
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
This trace looks a lot like the race, and:
{"type": "event", "event": "output", "body": {"category": "stdout", "output": "
File
\"/data/vries/gdb/leap-15-4/build/gdb/data-directory/python/gdb/dap/server.py\",
line 115, in main_loop\n"}, "seq": 7}
the line number here seems wrong, like it's from the version without
the race patch. Did you maybe not "make" after applying? The
test suite picks up the Python code from data-directory so a build
is needed before running the tests.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-23 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 16:02 [Bug gdb/30268] New: " vries at gcc dot gnu.org
2023-03-23 18:42 ` tromey at sourceware dot org [this message]
2023-03-23 21:50 ` [Bug gdb/30268] " vries at gcc dot gnu.org
2023-03-24 13:59 ` 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-30268-4717-2AzuHaS5Py@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).