public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cel at us dot ibm.com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29927] reverse-finish requires two reverse next instructions to reach previous source line
Date: Wed, 11 Jan 2023 19:08:47 +0000 [thread overview]
Message-ID: <bug-29927-4717-ZAVABpUSbW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29927-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29927
--- Comment #1 from Carl E Love <cel at us dot ibm.com> ---
The finish command when executing in reverse does not work on PowerPC
correctly. GDB doesn't stop at the caller. It will go back to the previous
breakpoint or stop when it reaches the beginning of the log file.
PowerPC has multiple entry points. GDB does not handle them properly when
doing a reverse-finish.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-11 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 16:56 [Bug gdb/29927] New: " cel at us dot ibm.com
2023-01-11 19:08 ` cel at us dot ibm.com [this message]
2023-01-11 19:12 ` [Bug gdb/29927] " cel at us dot ibm.com
2023-01-17 16:47 ` cvs-commit at gcc dot gnu.org
2023-01-17 16:47 ` cvs-commit at gcc dot gnu.org
2023-01-17 16:50 ` cel at us dot ibm.com
2023-01-17 16:52 ` cel at us dot ibm.com
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-29927-4717-ZAVABpUSbW@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).