From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BD5DD3858408; Mon, 22 Jan 2024 16:00:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BD5DD3858408 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1705939207; bh=nXbTUD2B0aipmZHzA28TAi0XDypNiqvx2XTyLuecOpg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=FQczOzjSyhGYw1X0aXIExCuKjzi6qlYD1FjsJGeEBuyP2WRVjlxUpMtnYNpVGykKA yV72yBkJFQgfVs8R/92JUL0ZJVHIC2xxe1iCZ9mSYjCmlkAHfwvz1PFQ/gIjWio70o 766sUBpXDY2fGPaqRcDDYwgWcCmQ9NZsFWFWBdAc= From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug dap/31217] dap throws exception when trying to rerun session Date: Mon, 22 Jan 2024 16:00:07 +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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: tromey 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=3D31217 --- Comment #9 from Sourceware Commits --- The master branch has been updated by Tom Tromey : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D46bdb641642d= 20307521f5db2e1f1c7dcc49d5a7 commit 46bdb641642d20307521f5db2e1f1c7dcc49d5a7 Author: Tom Tromey Date: Wed Jan 10 12:51:10 2024 -0700 Handle EOF more gracefully in DAP A user pointed out that gdb will print a Python exception when it gets an EOF in DAP mode. And, it turns out that an EOF like this also causes gdb not to exit. This is due to the refactoring that moved the JSON reader to its own thread -- previously this caused an exception to propagate and cause an exit, but now it just leaves the reader hung. This patch fixes these problems by arranging to handle EOF more gracefully. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31217 --=20 You are receiving this mail because: You are on the CC list for the bug.=