From: Carl Love via Gdb-patches <gdb-patches@sourceware.org>
To: Simon Marchi <simark@simark.ca>,
Bruno Larsen <blarsen@redhat.com>,
gdb-patches@sourceware.org,
UlrichWeigand <Ulrich.Weigand@de.ibm.com>,
pedro@palves.net
Cc: luis.machado@arm.com, cel@us.ibm.com
Subject: [PATCH 0/2] Fix reverse stepping multiple contiguous PC ranges over the line table.
Date: Mon, 07 Aug 2023 11:54:20 -0700 [thread overview]
Message-ID: <3a46ac42391707325ee2aab900d13bce05c8a0b8.camel@us.ibm.com> (raw)
GDB maintainers:
Per recent discussions with Bruno on how gdb should behave when reverse
stepping from a function call to the previous line:
https://sourceware.org/pipermail/gdb-patches/2023-July/201035.html
I have updated the second patch in the series to address his comments.
The current behavior of gdb when executing in reverse is gdb stops at
the call to a function, then a reverse-step or reverse-next stops at
the beginning of the same line instead of the previous line. Bruno
pointed out that gdb on clang stops at the previous line not at the
beginning of the line.
The first patch in the series has not been changed. I am reposting it
along with the second patch so it doesn't get lost.
The patch series has been tested on Power10 LE and on X86-64.
Carl
next reply other threads:[~2023-08-07 18:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 18:54 Carl Love via Gdb-patches [this message]
2023-08-07 19:03 ` [PATCH 1/2 ver 2] " Carl Love via Gdb-patches
2023-08-08 10:04 ` Guinevere Larsen via Gdb-patches
2023-08-08 15:38 ` Carl Love via Gdb-patches
2023-08-08 15:45 ` Guinevere Larsen via Gdb-patches
2023-08-07 19:03 ` [PATCH 2/2 ver 7] " Carl Love via Gdb-patches
2023-08-08 14:14 ` Guinevere Larsen via Gdb-patches
2023-08-08 15:52 ` Carl Love via Gdb-patches
2023-08-25 15:50 [PATCH 0/2] " Carl Love via Gdb-patches
2023-08-29 12:28 ` Guinevere Larsen via Gdb-patches
2023-08-29 18:55 ` Carl Love via Gdb-patches
2023-09-05 15:12 ` Carl Love via Gdb-patches
2023-09-25 22:15 ` Carl Love via Gdb-patches
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=3a46ac42391707325ee2aab900d13bce05c8a0b8.camel@us.ibm.com \
--to=gdb-patches@sourceware.org \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=blarsen@redhat.com \
--cc=cel@us.ibm.com \
--cc=luis.machado@arm.com \
--cc=pedro@palves.net \
--cc=simark@simark.ca \
/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