* Fix 16.0 handling. - Patches added: * gdb-testsuite-fix-gdb.python-py-format-string.exp-wi.patch * gdb-testsuite-fix-gdb.python-py-mi-cmd.exp-with-pyth.patch * gdb-testsuite-fix-gdb.ada-mi_task_arg.exp-on-arm-lin.patch * gdb-testsuite-fix-regexp-in-gdb.ada-mi_var_access.ex.patch * gdb-testsuite-check-gnatmake-version-in-gdb.ada-scal.patch * gdb-testsuite-fix-gdb.arch-arm-pseudo-unwind.exp-wit.patch * gdb-symtab-fix-target-type-of-complex-long-double-on.patch * gdb-testsuite-don-t-use-set-auto-solib-add-off.patch * gdb-tdep-fix-arm-thumb2-hw-breakpoint.patch * gdb-testsuite-fix-gdb.cp-m-static.exp-on-arm.patch * gdb-testsuite-fix-gdb.dwarf2-dw2-fixed-point.exp-on-.patch * gdb-testsuite-fix-gdb.dwarf2-dw2-lines.exp-on-arm-li.patch * gdb-exp-fix-gdb.fortran-intrinsics.exp-fail-on-arm.patch * gdb-tdep-handle-sycall-statx-for-arm-linux.patch * gdb-tdep-fix-recording-of-t1-push.patch * gdb-tdep-handle-syscall-clock_gettime64-for-arm-linu.patch * fix-gdb.dwarf2-shortpiece.exp-on-s390x.patch * handle-address-class-annotation-for-s390x-in-some-te.patch * fix-gdb.dap-step-out.exp-on-s390x.patch * use-setvariable-in-gdb.dap-scopes.exp.patch * fix-gdb.base-finish-pretty.exp-on-s390x.patch * fix-gdb.base-readnever.exp-on-s390x.patch * add-dwarf_expr_piece.op.patch * add-gdbarch_dwarf2_reg_piece_offset-hook.patch * fix-gdb.base-store.exp-on-s390x.patch * fix-gdb.ada-o2_float_param.exp-on-s390x-linux.patch * gdb-testsuite-fix-gdb.base-branch-to-self.exp-on-arm.patch * gdb-tdep-fix-gdb.cp-non-trivial-retval.exp-on-riscv6.patch * gdb-testsuite-fix-gdb.cp-non-trivial-retval.exp-on-a.patch * gdb-testsuite-fix-gdb.rust-completion.exp-timeout-on.patch * gdb-testsuite-require-supports_process_record-in-gdb.patch * gdb-testsuite-fix-regexp-in-gdb.arch-i386-disp-step-.patch * gdb-testsuite-fix-gdb.arch-arm-single-step-kernel-he.patch * gdb-testsuite-fix-gdb.python-py-format-address.exp-o.patch * gdb-testsuite-fix-gdb.arch-riscv-tdesc-regs.exp.patch * gdb-testsuite-fix-gdb.base-list-dot-nodebug-and-make.patch * gdb-testsuite-fix-gdb.base-list-dot-nodebug.exp-on-o.patch * gdb-testsuite-fix-gdb.base-empty-host-env-vars.exp.patch * gdb-prune-inferior-after-switching-inferior.patch * gdb-testsuite-use-nostdlib-in-gdb.base-list-dot-node.patch * gdb-testsuite-fix-timeout-in-gdb.mi-mi-multi-command.patch * gdb-testsuite-require-can_spawn_for_attach-in-gdb.ba.patch * fixup-gdb-6.5-gcore-buffer-limit-test.patch * gdb-testsuite-fix-gdb.ada-big_packed_array.exp-on-s3.patch * gdb-testsuite-fix-gdb.ada-convvar_comp.exp-on-s390x-.patch * gdb-testsuite-fix-regexp-in-gdb.threads-stepi-over-c.patch OBS-URL: https://build.opensuse.org/package/show/devel:gcc/gdb?expand=0&rev=437
97 lines
2.8 KiB
Diff
97 lines
2.8 KiB
Diff
From 9625fc9c035b75f7e55350ad72c37ce1b7e8fe55 Mon Sep 17 00:00:00 2001
|
|
From: Tom de Vries <tdevries@suse.de>
|
|
Date: Wed, 22 Jan 2025 10:46:08 +0100
|
|
Subject: [PATCH 27/46] [gdb/testsuite] Fix gdb.base/branch-to-self.exp on
|
|
arm-linux
|
|
|
|
On arm-linux (ubuntu 24.04 with gcc 13.3.0) with target board unix/-marm and
|
|
test-case gdb.base/branch-to-self.exp I run into:
|
|
...
|
|
(gdb) continue^M
|
|
Continuing.^M
|
|
^M
|
|
Breakpoint 2, main () at branch-to-self.c:38^M
|
|
38 for (;;); /* loop-line */^M
|
|
(gdb) PASS: $exp: single-step: continue to breakpoint: hit breakpoint
|
|
si^M
|
|
0x0040058c 38 for (;;); /* loop-line */^M
|
|
(gdb) FAIL: $exp: single-step: si
|
|
...
|
|
|
|
In contrast, on the same machine but with debian testing and gcc 14.2.0 we have:
|
|
...
|
|
(gdb) continue^M
|
|
Continuing.^M
|
|
^M
|
|
Breakpoint 2, main () at branch-to-self.c:38^M
|
|
38 for (;;); /* loop-line */^M
|
|
(gdb) PASS: $exp: single-step: continue to breakpoint: hit breakpoint
|
|
si^M
|
|
^M
|
|
Breakpoint 2, main () at branch-to-self.c:38^M
|
|
38 for (;;); /* loop-line */^M
|
|
(gdb) PASS: $exp: single-step: stepi
|
|
...
|
|
|
|
The difference is in the instruction(s) generated for the loop.
|
|
|
|
In the passing case, we have:
|
|
...
|
|
588: eafffffe b 588 <main+0x24>
|
|
...
|
|
and in the failing case:
|
|
...
|
|
588: e320f000 nop {0}
|
|
58c: eafffffd b 588 <main+0x24>
|
|
...
|
|
|
|
The purpose of this part of the test-case is to:
|
|
- generate a branch instruction that jumps to itself, and
|
|
- set a breakpoint on it, and check that stepi-ing from that breakpoint
|
|
triggers the breakpoint again.
|
|
|
|
As we can see, in the failing case we failed to generate a branch instruction
|
|
that jumps to itself, and consequently we cannot expect to hit the breakpoint
|
|
again after issuing a single si.
|
|
|
|
Fix this by issuing stepi until we hit the breakpoint.
|
|
|
|
Tested on arm-linux.
|
|
|
|
Reviewed-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
|
|
---
|
|
gdb/testsuite/gdb.base/branch-to-self.exp | 17 ++++++++++++++++-
|
|
1 file changed, 16 insertions(+), 1 deletion(-)
|
|
|
|
diff --git a/gdb/testsuite/gdb.base/branch-to-self.exp b/gdb/testsuite/gdb.base/branch-to-self.exp
|
|
index 9b4f7467498..71859d71e0d 100644
|
|
--- a/gdb/testsuite/gdb.base/branch-to-self.exp
|
|
+++ b/gdb/testsuite/gdb.base/branch-to-self.exp
|
|
@@ -35,7 +35,22 @@ with_test_prefix "single-step" {
|
|
gdb_test "break ${testfile}.c:${line_num}" "Breakpoint .*" \
|
|
"set breakpoint"
|
|
gdb_continue_to_breakpoint "hit breakpoint"
|
|
- gdb_test "si" ".*${testfile}.c:${line_num}.*"
|
|
+
|
|
+ set stepi_count 1
|
|
+ gdb_test_multiple "stepi" "" {
|
|
+ -re -wrap ".*${testfile}.c:${line_num}.*" {
|
|
+ pass $gdb_test_name
|
|
+ }
|
|
+ -re -wrap "" {
|
|
+ if { $stepi_count == 10 } {
|
|
+ fail $gdb_test_name
|
|
+ } else {
|
|
+ incr stepi_count
|
|
+ send_gdb "stepi\n"
|
|
+ exp_continue
|
|
+ }
|
|
+ }
|
|
+ }
|
|
}
|
|
|
|
with_test_prefix "break-cond" {
|
|
--
|
|
2.43.0
|
|
|