qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: John Reiser <jreiser@BitWagon.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] bug: qemu-0.9.0 emulating mipsel (32-bit R3000) on amd64
Date: Sun, 6 May 2007 21:04:52 +0100	[thread overview]
Message-ID: <20070506200452.GA32686@networkno.de> (raw)
In-Reply-To: <463E2234.3040508@BitWagon.com>

John Reiser wrote:
> Hi,
> 
> qemu-0.9.0 compiled and running on Debian 2.6.18-4-amd64,
> [compiled by gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)],
> emulating Debian 2.6.18-4-qemu mipsel (32-bit MIPS R3000 little endian),
> errs when gdb 6.4.90-debian (running on the emulated mipsel)
> single-steps the user-mode instruction:
> 	lw      a2,-44(s7)
> After single-stepping the 'lw', then register a2 contains garbage
> instead of the memory contents at address -44(s7).

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


Thiemo

  reply	other threads:[~2007-05-06 20: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 [this message]
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     ` [Qemu-devel] bug: " Stefan Weil
2007-05-08 23:50   ` 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=20070506200452.GA32686@networkno.de \
    --to=ths@networkno.de \
    --cc=jreiser@BitWagon.com \
    --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).