From: Cole Robinson <crobinso@redhat.com>
To: "Marcel Apfelbaum" <marcel.a@redhat.com>,
"Marcin Gibuła" <m.gibula@beyond.pl>
Cc: qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] qemu 2.0.0-rc2 crash
Date: Thu, 10 Apr 2014 14:37:37 -0400 [thread overview]
Message-ID: <5346E4F1.3020001@redhat.com> (raw)
In-Reply-To: <5346DFBC.2020701@redhat.com>
On 04/10/2014 02:15 PM, Cole Robinson wrote:
> On 04/10/2014 12:39 PM, Marcel Apfelbaum wrote:
>> On Thu, 2014-04-10 at 18:24 +0200, Marcin Gibuła wrote:
>>> W dniu 2014-04-10 15:43, Marcel Apfelbaum pisze:
>>>> On Thu, 2014-04-10 at 14:55 +0200, Marcin Gibuła wrote:
>>>>> Hi,
>>>>>
>>>>> I've been playing with QEMU 2.0-rc2 and found a crash that isn't there
>>>>> 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,
>>>
>>> Hi,
>>>
>>> yes, it's on development environment. If you could point me to some
>>> 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
>> 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.
>
> Actually I was just independently bisecting this :) Culprit is:
>
> commit 9561fda8d90e176bef598ba87c42a1bd6ad03ef7
> Author: Stefan Hajnoczi <stefanha@redhat.com>
> Date: Wed Mar 19 08:58:55 2014 +0100
>
> qom: Make QOM link property unref optional
>
> Simple reproducer:
>
> ./x86_64-softmmu/qemu-system-x86_64 -qmp unix:./qmp.sock,server
>
> ./scripts/qmp/qmp-shell ./qmp.sock
> (QEMU) qom-list path=//machine/i440fx/pci.0/child[2]
>
> Seems like trying to qom-list any link property will crash
>
I think this is the fix;
next prev parent reply other threads:[~2014-04-10 18:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 12:55 [Qemu-devel] qemu 2.0.0-rc2 crash Marcin Gibuła
2014-04-10 13:43 ` Marcel Apfelbaum
2014-04-10 16:24 ` Marcin Gibuła
2014-04-10 16:39 ` Marcel Apfelbaum
2014-04-10 18:15 ` Cole Robinson
2014-04-10 18:37 ` Cole Robinson [this message]
2014-04-10 18:38 ` Cole Robinson
2014-04-10 18:46 ` Marcel Apfelbaum
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=5346E4F1.3020001@redhat.com \
--to=crobinso@redhat.com \
--cc=afaerber@suse.de \
--cc=m.gibula@beyond.pl \
--cc=marcel.a@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).