From: Avi Kivity <avi@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Consistent crasher on reboot / shutdown
Date: Thu, 08 Sep 2011 12:54:55 +0300 [thread overview]
Message-ID: <4E6890EF.80508@redhat.com> (raw)
#0 0x00007f0f5da502c4 in malloc_consolidate.part.3 () from /lib64/libc.so.6
#1 0x00007f0f5da51274 in _int_malloc () from /lib64/libc.so.6
#2 0x00007f0f5da53b00 in malloc () from /lib64/libc.so.6
#3 0x000000000066cfec in malloc_and_trace (n_bytes=4120) at
/build/home/tlv/akivity/qemu/vl.c:2154
#4 0x00007f0f5fbdc1de in ?? () from /lib64/libglib-2.0.so.0
#5 0x00007f0f5fbdc668 in g_malloc0 () from /lib64/libglib-2.0.so.0
#6 0x00000000004f7e67 in qdict_new () at qdict.c:38
#7 0x00000000005e31e8 in handle_user_command (mon=0x2fccc30,
cmdline=0x2fcd0b0 "help") at /build/home/tlv/akivity/qemu/monitor.c:4532
#8 0x00000000005e4ed1 in monitor_command_cb (mon=0x2fccc30,
cmdline=0x2fcd0b0 "help", opaque=0x0) at
/build/home/tlv/akivity/qemu/monitor.c:5190
#9 0x000000000050b04c in readline_handle_byte (rs=0x2fcd0b0, ch=10) at
readline.c:370
#10 0x00000000005e4e15 in monitor_read (opaque=0x2fccc30,
buf=0x7fff0a383860 "\n", size=1) at
/build/home/tlv/akivity/qemu/monitor.c:5176
#11 0x00000000004f8ff9 in qemu_chr_be_write (s=0x2e53ae0,
buf=0x7fff0a383860 "\n", len=1) at qemu-char.c:163
#12 0x00000000004fcb57 in tcp_chr_read (opaque=0x2e53ae0) at
qemu-char.c:2106
#13 0x000000000046d87d in qemu_iohandler_poll (readfds=0x7fff0a384920,
writefds=0x7fff0a3849a0, xfds=0x7fff0a384a20, ret=1) at iohandler.c:175
#14 0x000000000066b4cc in main_loop_wait (nonblocking=0) at
/build/home/tlv/akivity/qemu/vl.c:1438
#15 0x000000000066b59c in main_loop () at
/build/home/tlv/akivity/qemu/vl.c:1469
#16 0x00000000006701e5 in main (argc=23, argv=0x7fff0a384ee8,
envp=0x7fff0a384fa8) at /build/home/tlv/akivity/qemu/vl.c:3491
--
error compiling committee.c: too many arguments to function
reply other threads:[~2011-09-08 9:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E6890EF.80508@redhat.com \
--to=avi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.