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 tdep/29815] New: [gdb/tdep, powerpc64le] FAIL: gdb.reverse/finish-reverse-bkpt.exp: reverse-finish from void_func trips breakpoint at entry Date: Mon, 21 Nov 2022 13:54:35 +0000 [thread overview] Message-ID: <bug-29815-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29815 Bug ID: 29815 Summary: [gdb/tdep, powerpc64le] FAIL: gdb.reverse/finish-reverse-bkpt.exp: reverse-finish from void_func trips breakpoint at entry Product: gdb Version: 12.1 Status: NEW Severity: normal Priority: P2 Component: tdep Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- With a gdb 12.1-based package, on powerpc64le I run into: ... FAIL: gdb.reverse/finish-reverse-bkpt.exp: reverse-finish from void_func trips breakpoint at entry FAIL: gdb.reverse/finish-reverse-bkpt.exp: no spurious proceed after breakpoint stop FAIL: gdb.reverse/next-reverse-bkpt-over-sr.exp: reverse-next over call trips user breakpoint at function entry FAIL: gdb.reverse/next-reverse-bkpt-over-sr.exp: stopped at the right callee call ... I'll try to reproduce on master, and if so, this might be a duplicate of the gdb.reverse FAILs Carl mentioned he's working on, so it might make sense to retest once those fixes are in. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-11-21 13:54 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-21 13:54 vries at gcc dot gnu.org [this message] 2022-11-21 16:30 ` [Bug tdep/29815] " vries at gcc dot gnu.org 2022-11-22 6:40 ` 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-29815-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).