From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id BCB243861871; Mon, 19 Feb 2024 08:47:53 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BCB243861871
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1708332473;
	bh=4kDvs0JFokVx4DCkk0pmIjnURgY4abl8XhuIxWva7m8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=BYE3xjGUvuWDjwChhwNUnzzCVPzlaeO7ZhOfMYZRHhvjuWSPawYIApLdj+5p2WEk0
	 C/5wmpHvZkzaMS8WKU7Jzf8Kw5TpeM7uia0oNjxk6OG9CrQznnHdLb7mmbGpHTD/Ph
	 LERA3jjEhmE99xD2p5NYGHrmX3uu2mWzsEfn90Jo=
From: "vries at gcc dot gnu.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: Mon, 19 Feb 2024 08:47:53 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: dap
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-31386-4717-T5uOzYKumZ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-31386-4717@http.sourceware.org/bugzilla/>
References: <bug-31386-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

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

--- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #5)
> I don't think you need a new event, just a new interpreter
> method; and then split the DAP initialization in two.

I managed to use the existing interpreter method pre_command_loop.

> Very early logging (before the "true" startup) probably
> isn't interesting anyway.

Not sure what the true start is, but AFAICT the first thing DAP does is log=
 a
message with the command it's about to run:
...
def run():
    """Main entry point for the DAP server.=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20
    This is called by the GDB DAP interpreter."""
    startup.exec_and_log("set python print-stack full")
...

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