From: Luiz Capitulino <lcapitulino@redhat.com>
To: Roy Tam <roytam@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] system_reset command cause assert failed
Date: Tue, 2 Feb 2010 10:58:46 -0200 [thread overview]
Message-ID: <20100202105846.11524da1@doriath> (raw)
In-Reply-To: <473191351002011735j29950b07hfa4fd06821849a8b@mail.gmail.com>
On Tue, 2 Feb 2010 09:35:16 +0800
Roy Tam <roytam@gmail.com> wrote:
> 2010/2/2 Luiz Capitulino <lcapitulino@redhat.com>:
> > On Tue, 2 Feb 2010 00:26:53 +0800
> > Roy Tam <roytam@gmail.com> wrote:
> >
> >> 2010/2/2 Luiz Capitulino <lcapitulino@redhat.com>:
> >>
> >> > Hm, I'm puzzled. Is this failing on malloc()? At least qemu_malloc()
> >> > is the last qemu's function I see in the logs.
> >> >
> >> > From now on I only see msvcrt functions...
> >> >
> >> > Maybe, you can type run on gdb, run system_reset on the
> >> > Monitor and then switch back to gdb and type bt?
> >> >
> >> source-less debugging seems better...
> >
> > As far as I can understand something bad happens while the parser
> > is processing the first "'" character of the qobject_from_jsonf()
> > call in monitor.c:4524.
> >
> > Strange. Can you try 'info pci', 'info block' and 'info version'?
> > Do they work?
> >
> > Maybe this is a refcount problem?
> >
> > Anthony, could you take a look too please?
> >
>
> rebuild with -gstabs -O1, you can see double free here:
Ok, so we have a double free and
> #0 qobject_to_qdict (obj=0x0) at qobject.h:108
> #1 0x004127ae in pci_device_print (mon=0x494c460, device=0x49696c0)
> at /home/roy/qemu/hw/pci.c:1165
a segfault.
I don't know what's happening, I'll have to run QEMU on windows and
try to reproduce it.
next prev parent reply other threads:[~2010-02-02 12:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 8:28 [Qemu-devel] system_reset command cause assert failed Roy Tam
2010-02-01 12:17 ` Luiz Capitulino
2010-02-01 12:36 ` Roy Tam
2010-02-01 13:22 ` Luiz Capitulino
2010-02-01 13:42 ` Roy Tam
2010-02-01 16:02 ` Luiz Capitulino
2010-02-01 16:26 ` Roy Tam
2010-02-01 18:58 ` Luiz Capitulino
2010-02-02 1:35 ` Roy Tam
2010-02-02 12:58 ` Luiz Capitulino [this message]
2010-02-03 2:09 ` Roy Tam
2010-02-03 12:26 ` Luiz Capitulino
2010-02-04 1:39 ` Roy Tam
2010-02-01 16:33 ` Roy Tam
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=20100202105846.11524da1@doriath \
--to=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=roytam@gmail.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).