aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.dwarf2
diff options
context:
space:
mode:
authorGuinevere Larsen <blarsen@redhat.com>2023-09-01 13:47:32 +0200
committerGuinevere Larsen <blarsen@redhat.com>2023-11-20 10:54:03 +0100
commitbf2813aff8f2988ad3d53e819a0415abf295c91f (patch)
tree05d1bbc97043c285887ee94f602d16651dcfd076 /gdb/testsuite/gdb.dwarf2
parent11788869e0a3713e847733be8712e4b3b5e4dfd9 (diff)
downloadgdb-bf2813aff8f2988ad3d53e819a0415abf295c91f.zip
gdb-bf2813aff8f2988ad3d53e819a0415abf295c91f.tar.gz
gdb-bf2813aff8f2988ad3d53e819a0415abf295c91f.tar.bz2
gdb/record: print frame information when exiting a recursive call
Currently, when GDB is reverse stepping out of a function into the same function due to a recursive call, it doesn't print frame information, as reported by PR record/29178. This happens because when the inferior leaves the current frame, GDB decides to refresh the step information, clobbering the original step_frame_id, making it impossible to figure out later on that the frame has been changed. This commit changes GDB so that, if we notice we're in this exact situation, we won't refresh the step information. Because of implementation details, this change can cause some debug information to be read when it normally wouldn't before, which showed up as a regression on gdb.dwarf2/dw2-out-of-range-end-of-seq. Since that isn't a problem, the test was changed to allow for the new output. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29178 Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'gdb/testsuite/gdb.dwarf2')
-rw-r--r--gdb/testsuite/gdb.dwarf2/dw2-out-of-range-end-of-seq.exp2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/testsuite/gdb.dwarf2/dw2-out-of-range-end-of-seq.exp b/gdb/testsuite/gdb.dwarf2/dw2-out-of-range-end-of-seq.exp
index d2c28a8..8b4e796 100644
--- a/gdb/testsuite/gdb.dwarf2/dw2-out-of-range-end-of-seq.exp
+++ b/gdb/testsuite/gdb.dwarf2/dw2-out-of-range-end-of-seq.exp
@@ -84,7 +84,7 @@ if ![runto_main] {
}
set test "END with address 1 eliminated"
-gdb_test_multiple "maint info line-table $srcfile$" $test {
+gdb_test_multiple "maint info line-table \\b$srcfile$" $test {
-re -wrap "END *0x0*1 *$hex *Y *\r\n.*" {
fail $gdb_test_name
}