From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id EF7133858C52; Thu, 29 Feb 2024 11:34:06 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EF7133858C52 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1709206446; bh=/3M0KhoJipqP/eCOrZ1svmLRmfXp4xzkS/rLIq0eWOY=; h=From:To:Subject:Date:From; b=uGgUx+GzctYmPRRQq2kJR8pNPzcd1YsTgtuxRdrga0SrviSloq2VjfBskZHlpC5CQ A2VCCRNlTve+ZBEFN5KHJFCldZzqxTisFaZAcgPaJhYTwSrcbfQAMWR1ErFEgvGrzP YiV3suoV/oUnJShOI49gUAyhkQiQTZjU6GkuWjsE= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug dap/31434] New: [gdb/dap, testsuite] Test race of cancellation with end of request Date: Thu, 29 Feb 2024 11:34:06 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: dap X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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=3D31434 Bug ID: 31434 Summary: [gdb/dap, testsuite] Test race of cancellation with end of request Product: gdb Version: HEAD Status: NEW Severity: enhancement Priority: P2 Component: dap Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- The test-case pause.exp is the only dap test-case that tests cancellation. There are three requests cancelled: - a continue - a loop in gdb - a loop in python For all three, I think the race between cancellation and start of request is excercised. For the first one, the cancellation is caught by _on_stop, so the end of request is only reached via normal return. For the last two, since both of them hang, the end of request is only reach= ed through cancellation. Consequently, the race between cancellation and end of request is currently untested. --=20 You are receiving this mail because: You are on the CC list for the bug.=