From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org, magnus.damm@gmail.com
Subject: Re: [Qemu-devel] sh4: more patches
Date: Mon, 25 Jun 2007 18:28:22 +0300 [thread overview]
Message-ID: <f43fc5580706250828j7a5b1812p55d22a3394404a83@mail.gmail.com> (raw)
In-Reply-To: <aec7e5c30706220044u5b4ae7felc64ed595454ebb37@mail.gmail.com>
On 6/22/07, Magnus Damm <magnus.damm@gmail.com> wrote:
> The method used to locate emulation bugs may be of value for other
> fellow qemu hackers. I've written a small gdb script that single steps
> in an endless loop dumping registers between each instruction. Then
> I've used this script on both real target hardware (using gdbserver)
> and using the gdbstub provided by qemu. Finally the traces have been
> compared. I have more patches for this if anyone is interested...
I'm interested in the scripts, those could be helpful to get Sparc64
bugs exterminated.
next prev parent reply other threads:[~2007-06-25 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 7:44 [Qemu-devel] sh4: more patches Magnus Damm
2007-06-22 11:48 ` Thiemo Seufer
2007-06-25 6:42 ` Magnus Damm
2007-06-25 12:01 ` Thiemo Seufer
2007-07-04 4:19 ` Magnus Damm
2007-07-25 1:02 ` Paul Mundt
2007-06-25 15:28 ` Blue Swirl [this message]
2007-07-04 4:44 ` Magnus Damm
2007-07-04 18:01 ` Blue Swirl
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=f43fc5580706250828j7a5b1812p55d22a3394404a83@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=magnus.damm@gmail.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).