diff options
author | Tom de Vries <tdevries@suse.de> | 2022-11-28 17:18:47 +0100 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2022-11-28 17:18:47 +0100 |
commit | b4bb9faa78c7454e9aafa4fbdbf76e4206acd14a (patch) | |
tree | bad36f6cf0f2e7559ab2c6a420c266da8c8b8721 /gdb/guile/scm-iterator.c | |
parent | af31506c31a59a6edbb13498d6075fa704b801cd (diff) | |
download | gdb-b4bb9faa78c7454e9aafa4fbdbf76e4206acd14a.zip gdb-b4bb9faa78c7454e9aafa4fbdbf76e4206acd14a.tar.gz gdb-b4bb9faa78c7454e9aafa4fbdbf76e4206acd14a.tar.bz2 |
[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.
Diffstat (limited to 'gdb/guile/scm-iterator.c')
0 files changed, 0 insertions, 0 deletions