From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48278)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <marcel.a@redhat.com>) id 1WYI0J-0004ff-8K
	for qemu-devel@nongnu.org; Thu, 10 Apr 2014 12:39:12 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <marcel.a@redhat.com>) id 1WYI0E-0003SA-LN
	for qemu-devel@nongnu.org; Thu, 10 Apr 2014 12:39:07 -0400
Received: from mx1.redhat.com ([209.132.183.28]:52466)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <marcel.a@redhat.com>) id 1WYI0E-0003S1-5t
	for qemu-devel@nongnu.org; Thu, 10 Apr 2014 12:39:02 -0400
Message-ID: <1397147966.28469.28.camel@localhost.localdomain>
From: Marcel Apfelbaum <marcel.a@redhat.com>
Date: Thu, 10 Apr 2014 19:39:26 +0300
In-Reply-To: <5346C5BF.8030706@beyond.pl>
References: <534694D3.9040504@beyond.pl>
	<1397137408.28469.3.camel@localhost.localdomain>
	<5346C5BF.8030706@beyond.pl>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] qemu 2.0.0-rc2 crash
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Marcin =?UTF-8?Q?Gibu=C5=82a?= <m.gibula@beyond.pl>
Cc: qemu-devel@nongnu.org

On Thu, 2014-04-10 at 18:24 +0200, Marcin Gibu=C5=82a wrote:
> W dniu 2014-04-10 15:43, Marcel Apfelbaum pisze:
> > On Thu, 2014-04-10 at 14:55 +0200, Marcin Gibu=C5=82a wrote:
> >> Hi,
> >>
> >> I've been playing with QEMU 2.0-rc2 and found a crash that isn't the=
re
> >> in 1.7.1.
> > Hi Marcin,
> > Thanks for reporting the bug!
> >
> > Do you have a development environment?
> > If you do, and the reproduction is fast (and you already have a setup=
),
> > a git bisect to find the problematic commit would be appreciated,
>=20
> Hi,
>=20
> yes, it's on development environment. If you could point me to some=20
> quick guide to bisecting qemu, I'll be happy to do it.

Sure! Thanks for helping.

1. Start:
     git bisect start
     git bisect good <commit hash or tag name of the version that works> =
(Ex: v1.7.1)
     git bisect bad <commit hash or tag name of the non working version> =
(Ex: HEAD)
2. Git will checkout commits for you and you have to check and answer:
     git bisect good or git bisect bad=20
3. Git will show you the first bad commit.

A more detailed version here:
http://git-scm.com/book/en/Git-Tools-Debugging-with-Git
Look for git-bisect.

Thanks,
Marcel

>=20