From: Aurelien Jarno <aurelien@aurel32.net>
To: Jamie Lokier <jamie@shareable.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Bug] qemu-system-ppc: "invalid/unsupported opcode" during debug session
Date: Sun, 28 Feb 2010 16:29:20 +0100 [thread overview]
Message-ID: <20100228152920.GC8952@hall.aurel32.net> (raw)
In-Reply-To: <20100228152542.GA28486@shareable.org>
On Sun, Feb 28, 2010 at 03:25:42PM +0000, Jamie Lokier wrote:
> Aurelien Jarno wrote:
> > It is not a full fix, as the OS can actually use any instruction that
> > always generate a trap (even a memory access) as an instruction barrier
> > to make sure the following instructions are never executed. This
> > actually affects all targets, but is unlikely to happen.
>
> I'm sure I've seen code wich intentionally accesses invalid memory,
> followed by non-instruction data such as a message to print. But I
> can't think where.
>
As Paul Brook explained, I am actually wrong. We don't generate an
exception in that case, but code that will generated an exception. If an
exception appears before, this code will never been executed.
So the best is to ignore this mail ;-)
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
prev parent reply other threads:[~2010-02-28 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B3A1B9D.7010004@mail.berlios.de>
2010-02-28 13:18 ` [Qemu-devel] [Bug] qemu-system-ppc: "invalid/unsupported opcode" during debug session Aurelien Jarno
2010-02-28 14:02 ` Paul Brook
2010-02-28 15:00 ` Aurelien Jarno
2010-02-28 15:25 ` Jamie Lokier
2010-02-28 15:29 ` Aurelien Jarno [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=20100228152920.GC8952@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=jamie@shareable.org \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).