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/27247] New: FAIL: gdb.python/py-finish-breakpoint2.exp: check FinishBreakpoint in catch() Date: Tue, 26 Jan 2021 10:04:06 +0000 [thread overview] Message-ID: <bug-27247-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27247 Bug ID: 27247 Summary: FAIL: gdb.python/py-finish-breakpoint2.exp: check FinishBreakpoint in catch() 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: --- [ Refiling https://sourceware.org/pipermail/gdb-patches/2021-January/175166.html as PR. ] When running test-case gdb.python/py-finish-breakpoint2.exp with target board unix/-m32, we run into: ... FAIL: gdb.python/py-finish-breakpoint2.exp: check FinishBreakpoint in catch() FAIL: gdb.python/py-finish-breakpoint2.exp: check finish BP removal FAIL: gdb.python/py-finish-breakpoint2.exp: continue to second exception FAIL: gdb.python/py-finish-breakpoint2.exp: set FinishBP after the exception ... The first FAIL in more detail: ... (gdb) continue^M Continuing.^M Exception #10^M ^M Breakpoint 3, throw_exception_1 (e=10) at py-finish-breakpoint2.cc:23^M 23 throw new int (e);^M (gdb) FAIL: gdb.python/py-finish-breakpoint2.exp: \ check FinishBreakpoint in catch() ... With -m64, the test passes. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-01-26 10:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-26 10:04 vries at gcc dot gnu.org [this message] 2021-01-26 10:06 ` [Bug python/27247] " vries at gcc dot gnu.org 2022-12-16 10:57 ` vries at gcc dot gnu.org 2022-12-16 11:38 ` vries at gcc dot gnu.org 2022-12-16 13:23 ` vries at gcc dot gnu.org 2022-12-31 7:51 ` cvs-commit at gcc dot gnu.org 2022-12-31 7:53 ` 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-27247-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).