From: Kevin Buettner <kevinb@redhat.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/testsuite] Handle SIGILL in two gdb.arch powerpc test-cases
Date: Tue, 2 Nov 2021 10:06:21 -0700 [thread overview]
Message-ID: <20211102100621.74a1d96a@f35-m1> (raw)
In-Reply-To: <20211029194516.GA27121@delia>
On Fri, 29 Oct 2021 21:45:18 +0200
Tom de Vries <tdevries@suse.de> wrote:
> 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.
>
> Any comments?
LGTM.
Kevin
prev parent reply other threads:[~2021-11-02 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 19:45 Tom de Vries
2021-11-02 15:41 ` will schmidt
2021-11-02 17:06 ` Kevin Buettner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211102100621.74a1d96a@f35-m1 \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).