public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/29909] New: [gdb] FinishBreakpoint calls stop instead of out_of_scope Date: Fri, 16 Dec 2022 11:58:56 +0000 [thread overview] Message-ID: <bug-29909-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29909 Bug ID: 29909 Summary: [gdb] FinishBreakpoint calls stop instead of out_of_scope Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- [ Filing this PR to mention it in a KFAIL in a patch I'm planning to submit. ] When running test-case gdb.python/py-finish-breakpoint2.exp, we get: ... (gdb) PASS: gdb.python/py-finish-breakpoint2.exp: set FinishBP after the exception continue^M Continuing.^M Exception #10^M stopped at ExceptionFinishBreakpoint^M (gdb) PASS: gdb.python/py-finish-breakpoint2.exp: check FinishBreakpoint in catch() ... A stop is reported, but instead the out-of-scope callback should be called. See also: - https://sourceware.org/pipermail/gdb-patches/2012-September/096347.html - https://sourceware.org/pipermail/gdb-patches/2021-January/175290.html -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-12-16 11:58 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-16 11:58 vries at gcc dot gnu.org [this message] 2022-12-16 13:25 ` [Bug python/29909] " vries at gcc dot gnu.org
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-29909-4717@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: linkBe 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).