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/31386] [gdb/dap] Race between dap startup and dap log file initialization
Date: Fri, 16 Feb 2024 02:48:23 +0000 [thread overview]
Message-ID: <bug-31386-4717-KrBOXZu33V@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31386-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31386
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Tom de Vries from comment #1)
> One way to address this is to keep the log in a string until a file is set.
That may never happen, so we'd end up accumulating a large string.
There should probably be some way for the DAP interpreter to not
start accepting requests until all the command-line options have
been handled. Maybe a new interpreter method is needed.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-02-16 2:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 19:45 [Bug dap/31386] New: " vries at gcc dot gnu.org
2024-02-15 20:05 ` [Bug dap/31386] " vries at gcc dot gnu.org
2024-02-16 2:48 ` tromey at sourceware dot org [this message]
2024-02-16 9:36 ` vries at gcc dot gnu.org
2024-02-16 11:46 ` vries at gcc dot gnu.org
2024-02-16 17:24 ` tromey at sourceware dot org
2024-02-19 8:25 ` vries at gcc dot gnu.org
2024-02-19 8:47 ` vries at gcc dot gnu.org
2024-02-22 10:35 ` cvs-commit at gcc dot gnu.org
2024-02-22 10:39 ` 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-31386-4717-KrBOXZu33V@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).