From: Tom de Vries Date: Mon, 28 Nov 2022 16:18:47 +0000 (+0100) Subject: [gdb/testsuite] Fix gdb.ada/out_of_line_in_inlined.exp for ppc64le X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=b4bb9faa78c7454e9aafa4fbdbf76e4206acd14a;p=binutils-gdb.git [gdb/testsuite] Fix gdb.ada/out_of_line_in_inlined.exp for ppc64le On powerpc64le-linux, with test-case gdb.ada/out_of_line_in_inlined.exp I run into: ... (gdb) run ^M Starting program: foo_o224_021-all ^M ^M Breakpoint 1, 0x0000000010002f48 in foo_o224_021.child1.child2 (s=...) at \ foo_o224_021.adb:24^M 24 function Child2 (S : String) return Boolean is -- STOP^M (gdb) FAIL: gdb.ada/out_of_line_in_inlined.exp: scenario=all: \ run to foo_o224_021.child1.child2 ... The breakpoint is correctly set at the local entry point, and given that the local entry point doesn't correspond to a line number entry, the instruction address of the breakpoint is shown. The problem is that test-case doesn't expect the breakpoint address. Fix this by allowing the breakpoint address to occur. Tested on powerpc64le-linux. --- diff --git a/gdb/testsuite/gdb.ada/out_of_line_in_inlined.exp b/gdb/testsuite/gdb.ada/out_of_line_in_inlined.exp index 4bdb4decaaf..621b04e179b 100644 --- a/gdb/testsuite/gdb.ada/out_of_line_in_inlined.exp +++ b/gdb/testsuite/gdb.ada/out_of_line_in_inlined.exp @@ -34,7 +34,7 @@ foreach_with_prefix scenario {all minimal} { gdb_run_cmd gdb_test "" \ - "Breakpoint $decimal, foo_o224_021\\.child1\\.child2 \\(s=\\.\\.\\.\\).*" \ + "Breakpoint $decimal, ($hex in )?foo_o224_021\\.child1\\.child2 \\(s=\\.\\.\\.\\).*" \ "run to foo_o224_021.child1.child2" set opt_addr_in "($hex in)?"