qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Roy Tam <roytam@gmail.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] system_reset command cause assert failed
Date: Tue, 2 Feb 2010 00:33:59 +0800	[thread overview]
Message-ID: <473191351002010833q5ab0275bs5a66fa524348d84e@mail.gmail.com> (raw)
In-Reply-To: <20100201140206.1f414f3f@doriath>

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?
>

for backtrace, I got Backtrace stopped.

(gdb) bt
#0  monitor_protocol_event (event=QEVENT_RESET, data=0x0) at
/home/roy/qemu/monitor.c:349
#1  0x0040f6f9 in monitor_protocol_event (event=4199152,
data=0xff0a0000) at /home/roy/qemu/monitor.c:349
Backtrace stopped: frame did not save the PC

and there's a double free at the end.

      parent reply	other threads:[~2010-02-01 16:34 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
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 [this message]

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=473191351002010833q5ab0275bs5a66fa524348d84e@mail.gmail.com \
    --to=roytam@gmail.com \
    --cc=lcapitulino@redhat.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).