public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug cli/25913] New: Command to step through line
@ 2020-05-03 11:31 vries at gcc dot gnu.org
2020-05-11 20:35 ` [Bug cli/25913] " ssbssa at sourceware dot org
2020-05-27 13:19 ` vries at gcc dot gnu.org
0 siblings, 2 replies; 3+ messages in thread
From: vries at gcc dot gnu.org @ 2020-05-03 11:31 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=25913
Bug ID: 25913
Summary: Command to step through line
Product: gdb
Version: HEAD
Status: NEW
Severity: enhancement
Priority: P2
Component: cli
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With gdb, we can step to the next line (step command) or next instruction
(stepi).
Consider the example from PR25911. We can step past line 6 with step, or step
through the instructions with stepi:
...
$ gdb a.out
Reading symbols from a.out...
(gdb) start
Temporary breakpoint 1 at 0x400496: file stmts-on-line.c, line 4.
Starting program: /data/gdb_versions/devel/a.out
Temporary breakpoint 1, main () at stmts-on-line.c:4
4 int a = 4;
(gdb) s
6 a = 5; a = 6; a = 7;
(gdb) si
6 a = 5; a = 6; a = 7;
(gdb) si
6 a = 5; a = 6; a = 7;
(gdb) si
8 return 0;
...
but with gcc-10, there's an intermediate level between line and instruction:
the "recommended breakpoint location".
So, propose to add a command, say stepc for "step column" to step through the
"recommended breakpoint locations", which can be on the same line but several
instructions apart.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug cli/25913] Command to step through line
2020-05-03 11:31 [Bug cli/25913] New: Command to step through line vries at gcc dot gnu.org
@ 2020-05-11 20:35 ` ssbssa at sourceware dot org
2020-05-27 13:19 ` vries at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: ssbssa at sourceware dot org @ 2020-05-11 20:35 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=25913
Hannes Domani <ssbssa at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ssbssa at sourceware dot org
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug cli/25913] Command to step through line
2020-05-03 11:31 [Bug cli/25913] New: Command to step through line vries at gcc dot gnu.org
2020-05-11 20:35 ` [Bug cli/25913] " ssbssa at sourceware dot org
@ 2020-05-27 13:19 ` vries at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: vries at gcc dot gnu.org @ 2020-05-27 13:19 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=25913
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
RFC implementing this:
https://sourceware.org/pipermail/gdb-patches/2020-May/168673.html
Older prototype (mentioned here:
https://sourceware.org/pipermail/gdb-patches/2020-May/168682.html):
https://github.com/hexa00/binutils-gdb/commits/statement-stepping
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-05-27 13:19 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-03 11:31 [Bug cli/25913] New: Command to step through line vries at gcc dot gnu.org
2020-05-11 20:35 ` [Bug cli/25913] " ssbssa at sourceware dot org
2020-05-27 13:19 ` vries at gcc dot gnu.org
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).