From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id AF04A3853D50; Fri, 18 Nov 2022 15:56:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AF04A3853D50 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1668787007; bh=/sG39GlG28ZSh2r8JQhpi8vgFYUwwnlsCZMrpRnufrw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=i4E1y351spG/PqnwUx1Dv50CO4ZGxlFNcjRtKTf9dCEXen5y998IRj1LXVRoYV9Qg 9Whw4u5csfC05t/YhTsxjfyW391eaDOWbNdtwcJDuVLlJonl+825fO8b35tjm4LG3x 86tDKzXTody42GyY/bYwJO92r+tsZNpnX7290wfI= From: "cvs-commit at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug python/18655] Python FinishBreakpoints are not deleted Date: Fri, 18 Nov 2022 15:56:42 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Version: HEAD 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: 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=3D18655 --- Comment #6 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Simon Marchi : https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D6533cbeeb831= 224e2d2dd2a7bea54b22b798fa39 commit 6533cbeeb831224e2d2dd2a7bea54b22b798fa39 Author: Johnson Sun Date: Fri Oct 21 01:49:18 2022 +0800 Fix deletion of FinishBreakpoints Currently, FinishBreakpoints are set at the return address of a frame b= ased on the `finish' command, and are meant to be temporary breakpoints. Howeve= r, they are not being cleaned up after use, as reported in PR python/18655. This was happening because the disposition of the breakpoint was not being set correctly. This commit fixes this issue by correctly setting the disposition in the post-stop hook of the breakpoint. It also adds a test to ensure this feature isn't regressed in the future. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=3D18655 --=20 You are receiving this mail because: You are on the CC list for the bug.=