aboutsummaryrefslogtreecommitdiff
path: root/gdb/cli
diff options
context:
space:
mode:
authorTom de Vries <tdevries@zinfandel-3.arch.suse.de>2021-11-02 18:55:32 +0100
committerTom de Vries <tdevries@suse.de>2021-11-02 18:55:32 +0100
commitd74dfa8f63c2bb951609ab671773354536543ac2 (patch)
treedd823525a7ce2dd64ad3d405e41ecf67ace66456 /gdb/cli
parentbd25c6eef8f1004fe54ee9c0b964f62497c84a08 (diff)
downloadgdb-d74dfa8f63c2bb951609ab671773354536543ac2.zip
gdb-d74dfa8f63c2bb951609ab671773354536543ac2.tar.gz
gdb-d74dfa8f63c2bb951609ab671773354536543ac2.tar.bz2
[gdb/testsuite] Handle SIGILL in two gdb.arch powerpc test-cases
On powerpc64le-linux, with test-case gdb.arch/powerpc-addpcis.exp I run into SIGILL: ... (gdb) PASS: gdb.arch/powerpc-addpcis.exp: get hexadecimal valueof "$r3" stepi^M ^M Program terminated with signal SIGILL, Illegal instruction.^M The program no longer exists.^M (gdb) PASS: gdb.arch/powerpc-addpcis.exp: set r4 ... because it's a power9 insn, and I'm running on a power8 machine. Fix this by handling the SIGILL. Likewise in gdb.arch/powerpc-lnia.exp. Tested on powerpc64le-linux.
Diffstat (limited to 'gdb/cli')
0 files changed, 0 insertions, 0 deletions