public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/18655] Python FinishBreakpoints are not deleted
Date: Fri, 18 Nov 2022 15:56:42 +0000	[thread overview]
Message-ID: <bug-18655-4717-BoscN2BwsL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18655-4717@http.sourceware.org/bugzilla/>

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

--- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Simon Marchi <simark@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6533cbeeb831224e2d2dd2a7bea54b22b798fa39

commit 6533cbeeb831224e2d2dd2a7bea54b22b798fa39
Author: Johnson Sun <j3.soon777@gmail.com>
Date:   Fri Oct 21 01:49:18 2022 +0800

    Fix deletion of FinishBreakpoints

    Currently, FinishBreakpoints are set at the return address of a frame based
on
    the `finish' command, and are meant to be temporary breakpoints. However,
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=18655

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

  parent reply	other threads:[~2022-11-18 15:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10 15:43 [Bug python/18655] New: GDB " simon.marchi at ericsson dot com
2015-07-10 15:43 ` [Bug python/18655] " simon.marchi at ericsson dot com
2015-07-10 15:44 ` simon.marchi at ericsson dot com
2015-07-10 18:17 ` [Bug python/18655] " simon.marchi at ericsson dot com
2015-07-10 18:52 ` andrew.burgess at embecosm dot com
2022-09-17  0:19 ` j3.soon777 at gmail dot com
2022-09-17  0:24 ` j3.soon777 at gmail dot com
2022-09-20 17:35 ` j3.soon777 at gmail dot com
2022-11-18 15:56 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-18 16:01 ` simark at simark dot ca

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-18655-4717-BoscN2BwsL@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).