qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Nigel Horne <njh@bandsman.co.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Mips guest
Date: Wed, 19 Sep 2007 10:43:04 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0709191037140.28395@racer.site> (raw)
In-Reply-To: <46F0EA2E.2080609@bandsman.co.uk>

Hi,

On Wed, 19 Sep 2007, Nigel Horne wrote:

> The latest CVS snapshot has broken MIPS emulation.
> 
> [...]
>
> Then it hangs.
> 
> The last time I tried this guest was a couple of weeks ago, or so, and 
> all was fine then.

It would be so good if you could bisect this.

If you have git, clone qemu from git://git.kernel.dk/data/git/qemu.git, 
and use something "git log" to identify a commit that is likely to be 
good.  The easiest way to proceed is then to copy the commit name (this 
40-character hex string), and use it in

	git bisect start
	git bisect good <that-string>
	git bisect bad HEAD

It will find the middle point between the two, which you should compile 
and test.  Depending on the outcome of the test, you should mark the 
current commit as "git bisect good" or "git bisect bad" (you do not need 
to say which commit, if it is the current you mean).

Eventually, this procedure will give you the bad commit, which then makes 
it easier to see what actually broke the MIPS guest for you.

Thanks,
Dscho

  reply	other threads:[~2007-09-19  9:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19  9:21 [Qemu-devel] Mips guest Nigel Horne
2007-09-19  9:43 ` Johannes Schindelin [this message]
2007-09-19 12:37   ` Nigel Horne
2007-09-19 12:53     ` Thiemo Seufer
2007-09-19 13:49       ` Nigel Horne
2007-09-19 14:33         ` Ronald
2007-09-19 15:07           ` Nigel Horne
2007-09-19 10:16 ` 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=Pine.LNX.4.64.0709191037140.28395@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=njh@bandsman.co.uk \
    --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).