From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 039D8385800B; Fri, 16 Feb 2024 17:24:33 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 039D8385800B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1708104274; bh=ZRXs5vfM/PUGjLKhw/zWdlZfHN7zFOfczCOo6pCqcyY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=OCyz9V5fYnBZr8YBFnvR61tgYLF3GVcYoSyIf5I87KJc6KJA/fVEWe+wyADthO6xy d+v271VWAT+akTW5g4RYzQSP/+a8w90YlSINtJjTgbg1bNF3C0U6RFSjamTiiaqSx8 ryra7pbCV04ec2WIQshMrmg8SWo0lBJnodsvLRvE= From: "tromey at sourceware dot 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 17:24:33 +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: tromey at sourceware dot 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: In-Reply-To: References: 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: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31386 --- Comment #5 from Tom Tromey --- I don't think you need a new event, just a new interpreter method; and then split the DAP initialization in two. Very early logging (before the "true" startup) probably isn't interesting anyway. --=20 You are receiving this mail because: You are on the CC list for the bug.=