From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH] [gdb] Fix missing print frame when stepping out of function
Date: Thu, 12 Mar 2026 13:02:11 +0100 [thread overview]
Message-ID: <20260312120211.3806600-1-tdevries@suse.de> (raw)
Consider test-case gdb.dwarf2/dw2-extend-inline-block.exp, specifically the
"contiguous block" prefix part, which can be stepped through like this:
...
$ gdb -q outputs/gdb.dwarf2/dw2-extend-inline-block/dw2-extend-inline-block-5
Reading symbols from dw2-extend-inline-block-5...
(gdb) start
...
Temporary breakpoint 1, main () at dw2-extend-inline-block.c:35
35 /* main:2 */
(gdb) s
36 /* main:3 */ foo (); /* foo call line */
(gdb)
foo () at dw2-extend-inline-block.c:26
26 /* foo:1 */
(gdb) s
27 /* foo:2 */
(gdb) s
28 /* foo:3 */
(gdb) s
main () at dw2-extend-inline-block.c:37
37 /* main:4 */
(gdb)
...
If we slightly modify the line program:
...
DW_LNE_set_address main_4
+ DW_LNS_advance_line 1
DW_LNS_copy
DW_LNE_set_address main_5
- DW_LNS_advance_line 1
DW_LNS_negate_stmt
DW_LNS_copy
...
we change the 36/0x401165 entry into a 37/0x401165 entry:
...
File name Line number Starting address View Stmt
dw2-extend-inline-block.c 34 0x401116 x
dw2-extend-inline-block.c 35 0x401129 x
dw2-extend-inline-block.c 26 0x401138 x
dw2-extend-inline-block.c 27 0x401147 x
dw2-extend-inline-block.c 28 0x401156 x
dw2-extend-inline-block.c 36 0x401156
-dw2-extend-inline-block.c 36 0x401165
+dw2-extend-inline-block.c 37 0x401165
dw2-extend-inline-block.c 37 0x401174 x
dw2-extend-inline-block.c 38 0x401183 x
dw2-extend-inline-block.c 39 0x401192 x
dw2-extend-inline-block.c 40 0x4011a1 x
dw2-extend-inline-block.c - 0x4011b7
...
As it happens, the fix to extend truncated inlined function blocks doesn't
work in this case. This is PR33930.
We can work around this by making sure that the inlined function block isn't
truncated in the first place:
...
- DW_AT_high_pc main_3 addr
+ DW_AT_high_pc main_4 addr
...
But then we still run into PR33981: the problem that gdb doesn't notify us
when stepping out of main:
...
(gdb) step^M
28 /* foo:3 */^M
(gdb) step^M
37 /* main:4 */^M
(gdb)
...
What happens is that the slightly different line program triggers a different
stepping path, which includes a case of "stepped to a different frame, but
it's not the start of a statement", which refreshes the stepping info and
consequently updates tp->control.step_frame_id to the frame id of main.
So by the time we're stopped at line 37, and are trying to figure out what to
print in print_stop_location, this condition evaluates to true:
...
if (tp->control.stop_step
&& (tp->control.step_frame_id
== get_frame_id (get_current_frame ()))
&& (tp->control.step_start_function
== find_symbol_for_pc (tp->stop_pc ())))
...
and we get:
...
/* Finished step in same frame and same file, just print source
line. */
source_flag = SRC_LINE;
...
It's good to realize here that because foo is inlined into main,
tp->control.step_start_function is not foo but main, so consequently the
step_start_function check (which checks if we are still in the same function)
also passes, even though we actually stepped from foo into main.
No longer refreshing the stepping info in the "stepped to a different frame,
but it's not the start of a statement" case does fix the problem.
But the refreshing is needed to be able to handle stepping out of say function
f1 into function f2 and immediately stepping back into f1 again. If we don't
refresh in between, it looks like we stayed in f1.
Fix this by:
- adding a new field thread_control_state::step_frame_id_changed,
- updating the new field in set_step_info when refreshing, and
- using the new field in print_stop_location.
Tested on x86_64-linux.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=33981
---
gdb/gdbthread.h | 4 ++
gdb/infrun.c | 10 ++++-
gdb/infrun.h | 5 ++-
.../gdb.dwarf2/dw2-extend-inline-block.exp | 45 +++++++++++++++++--
4 files changed, 57 insertions(+), 7 deletions(-)
diff --git a/gdb/gdbthread.h b/gdb/gdbthread.h
index 68d7aebbbf7..02cf8f01fca 100644
--- a/gdb/gdbthread.h
+++ b/gdb/gdbthread.h
@@ -146,6 +146,10 @@ struct thread_control_state
any inlined frames). */
struct frame_id step_stack_frame_id {};
+ /* True if step_frame_id was changed after the stepping command was
+ issued. */
+ bool step_frame_id_changed = false;
+
/* True if the thread is presently stepping over a breakpoint or
a watchpoint, either with an inline step over or a displaced (out
of line) step, and we're now expecting it to report a trap for
diff --git a/gdb/infrun.c b/gdb/infrun.c
index c05c2b0f42f..df55c9a3c66 100644
--- a/gdb/infrun.c
+++ b/gdb/infrun.c
@@ -3084,6 +3084,7 @@ clear_proceed_status_thread (struct thread_info *tp)
tp->control.step_range_end = 0;
tp->control.may_range_step = 0;
tp->control.step_frame_id = null_frame_id;
+ tp->control.step_frame_id_changed = false;
tp->control.step_stack_frame_id = null_frame_id;
tp->control.step_over_calls = STEP_OVER_UNDEBUGGABLE;
tp->control.step_start_function = nullptr;
@@ -4818,12 +4819,16 @@ fetch_inferior_event ()
void
set_step_info (thread_info *tp, const frame_info_ptr &frame,
- struct symtab_and_line sal)
+ struct symtab_and_line sal, bool refresh_p)
{
/* This can be removed once this function no longer implicitly relies on the
inferior_ptid value. */
gdb_assert (inferior_ptid == tp->ptid);
+ if (refresh_p
+ && tp->control.step_frame_id != null_frame_id
+ && tp->control.step_frame_id != get_frame_id (frame))
+ tp->control.step_frame_id_changed = true;
tp->control.step_frame_id = get_frame_id (frame);
tp->control.step_stack_frame_id = get_stack_frame_id (frame);
@@ -8331,7 +8336,7 @@ process_event_stop_test (struct execution_control_state *ecs)
paddress (gdbarch, ecs->event_thread->control.step_range_end),
ecs->event_thread->control.may_range_step);
if (refresh_step_info)
- set_step_info (ecs->event_thread, frame, stop_pc_sal);
+ set_step_info (ecs->event_thread, frame, stop_pc_sal, true);
infrun_debug_printf ("keep going");
@@ -9350,6 +9355,7 @@ print_stop_location (const target_waitstatus &ws)
should) carry around the function and does (or should) use
that when doing a frame comparison. */
if (tp->control.stop_step
+ && !tp->control.step_frame_id_changed
&& (tp->control.step_frame_id
== get_frame_id (get_current_frame ()))
&& (tp->control.step_start_function
diff --git a/gdb/infrun.h b/gdb/infrun.h
index 0a7cdadf1fa..7fc7523be3f 100644
--- a/gdb/infrun.h
+++ b/gdb/infrun.h
@@ -205,10 +205,11 @@ extern int thread_is_stepping_over_breakpoint (int thread);
triggers a non-steppable watchpoint. */
extern int stepping_past_nonsteppable_watchpoint (void);
-/* Record in TP the frame and location we're currently stepping through. */
+/* Record in TP the frame and location we're currently stepping through. If
+ REFRESH_P, we're refreshing step info. */
extern void set_step_info (thread_info *tp,
const frame_info_ptr &frame,
- struct symtab_and_line sal);
+ struct symtab_and_line sal, bool refresh_p = false);
/* Notify interpreters and observers that the current inferior has stopped with
signal SIG. */
diff --git a/gdb/testsuite/gdb.dwarf2/dw2-extend-inline-block.exp b/gdb/testsuite/gdb.dwarf2/dw2-extend-inline-block.exp
index 9e4798b53f3..3f92c1965d8 100644
--- a/gdb/testsuite/gdb.dwarf2/dw2-extend-inline-block.exp
+++ b/gdb/testsuite/gdb.dwarf2/dw2-extend-inline-block.exp
@@ -52,8 +52,11 @@ get_func_info main
# Create DWARF for the test. In this case, inline function 'foo' is created
# with a contiguous address range that needs extending.
-proc build_dwarf_for_contiguous_block { asm_file } {
+proc build_dwarf_for_contiguous_block { asm_file {range_correct 0} {variant 0}} {
Dwarf::assemble $asm_file {
+ upvar range_correct range_correct
+ upvar variant variant
+
declare_labels lines_table inline_func
cu { } {
@@ -83,7 +86,11 @@ proc build_dwarf_for_contiguous_block { asm_file } {
DW_AT_call_file 1 data1
DW_AT_call_line $::foo_call_line data1
DW_AT_low_pc main_1 addr
- DW_AT_high_pc main_3 addr
+ if {$range_correct} {
+ DW_AT_high_pc main_4 addr
+ } else {
+ DW_AT_high_pc main_3 addr
+ }
}
}
}
@@ -120,10 +127,15 @@ proc build_dwarf_for_contiguous_block { asm_file } {
DW_LNS_copy
DW_LNE_set_address main_4
+ if {$variant == 1} {
+ DW_LNS_advance_line 1
+ }
DW_LNS_copy
DW_LNE_set_address main_5
- DW_LNS_advance_line 1
+ if {$variant == 0} {
+ DW_LNS_advance_line 1
+ }
DW_LNS_negate_stmt
DW_LNS_copy
@@ -146,6 +158,22 @@ proc build_dwarf_for_contiguous_block { asm_file } {
}
}
+# Like build_dwarf_for_contiguous_block, but use a slightly different line
+# info by setting variant == 1.
+# Use range_correct 1, so we're not testing the fix for PR33930.
+
+proc build_dwarf_for_contiguous_block_2 { asm_file } {
+ return [build_dwarf_for_contiguous_block $asm_file 1 1]
+}
+
+# Like build_dwarf_for_contiguous_block, but use a slightly different line
+# info by setting variant == 1.
+# Use range_correct 0, so we're testing the fix for PR33930.
+
+proc build_dwarf_for_contiguous_block_3 { asm_file } {
+ return [build_dwarf_for_contiguous_block $asm_file 0 1]
+}
+
# Assuming GDB is stopped at the entry $pc for 'foo', use 'maint info
# blocks' to check the block for 'foo' is correct. This function checks
# 'foo' created by 'build_dwarf_for_contiguous_block'.
@@ -555,6 +583,12 @@ set test_list \
[list "contiguous block" \
build_dwarf_for_contiguous_block \
check_contiguous_block] \
+ [list "contiguous block 2" \
+ build_dwarf_for_contiguous_block_2 \
+ check_contiguous_block] \
+ [list "contiguous block 3" \
+ build_dwarf_for_contiguous_block_3 \
+ check_contiguous_block] \
]
# Run all the tests.
@@ -566,6 +600,11 @@ foreach test_spec $test_list {
set build_dwarf_func [lindex $test_spec 1]
set check_block_func [lindex $test_spec 2]
+ if {$build_dwarf_func == "build_dwarf_for_contiguous_block_3"} {
+ # Work around PR33930.
+ continue
+ }
+
with_test_prefix $prefix {
set asm_file [standard_output_file ${testfile}-${suffix}.S]
$build_dwarf_func $asm_file
base-commit: c8b798145ff623a87ec4d39015cf832b0160899d
--
2.51.0
next reply other threads:[~2026-03-12 12:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 12:02 Tom de Vries [this message]
2026-03-18 14:29 ` Andrew Burgess
2026-03-19 18:03 ` Tom de Vries
2026-03-31 13:27 ` Tom de Vries
2026-03-31 15:44 ` Andrew Burgess
2026-03-31 13:32 ` Tom de Vries
2026-04-03 15:17 ` Tom de Vries
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=20260312120211.3806600-1-tdevries@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@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