From: Stefan Weil <weil@mail.berlios.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] bug: qemu-0.9.0 emulating mipsel (32-bit R3000) on amd64
Date: Tue, 08 May 2007 20:03:49 +0200 [thread overview]
Message-ID: <4640BB85.60402@mail.berlios.de> (raw)
In-Reply-To: <20070507121310.GA18535@caradoc.them.org>
This won't help for the problems with MIPS FPU emulation, will it?
Both breakpoints and the FPU emulation in the Linux kernel use
self-modifying code, so there should be a general solution for
both (and more related) problems.
As long as this general solution is missing, the published code
patches help.
Stefan
Daniel Jacobowitz schrieb:
> On Sun, May 06, 2007 at 09:04:52PM +0100, Thiemo Seufer wrote:
>> This looks like another instance of "Qemu/MIPS doesn't handle
>> self-modifying code correctly" (the break instructions inserted
>> by gdb are exactly this).
>>
>> A gross workaround is
>> http://lists.nongnu.org/archive/html/qemu-devel/2007-05/msg00037.html
>
> Someone might want to try:
> http://lists.nongnu.org/archive/html/qemu-devel/2007-04/msg00514.html
next prev parent reply other threads:[~2007-05-08 18:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 18:45 [Qemu-devel] bug: qemu-0.9.0 emulating mipsel (32-bit R3000) on amd64 John Reiser
2007-05-06 20:04 ` Thiemo Seufer
2007-05-06 20:07 ` Thiemo Seufer
2007-05-07 12:13 ` Daniel Jacobowitz
2007-05-07 15:46 ` Paul Brook
2007-05-07 22:46 ` [Qemu-devel] workaround: " John Reiser
2007-05-07 23:03 ` Paul Brook
2007-05-07 23:08 ` Paul Brook
2007-05-08 18:03 ` Stefan Weil [this message]
2007-05-08 23:50 ` [Qemu-devel] bug: " John Reiser
2007-05-09 1:04 ` Thiemo Seufer
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=4640BB85.60402@mail.berlios.de \
--to=weil@mail.berlios.de \
--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).