From: Avi Kivity <avi@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] PPC* and Sparc32 crash
Date: Thu, 25 Aug 2011 22:31:12 +0300 [thread overview]
Message-ID: <4E56A300.8020805@redhat.com> (raw)
In-Reply-To: <CAAu8pHs+TXZirHqH1rYq3XD63b+pB6M1-YjdzHthvK1Uakxfvw@mail.gmail.com>
On 08/25/2011 08:33 PM, Blue Swirl wrote:
> (gdb) bt
> #0 0x00007ffff3da2165 in *__GI_raise (sig=<value optimized out>)
> at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
> #1 0x00007ffff3da4f70 in *__GI_abort () at abort.c:92
> #2 0x00007ffff3d9b2b1 in *__GI___assert_fail (
> assertion=0x5c7390 "info->qdev.size>= sizeof(SysBusDevice)",
> file=<value optimized out>, line=0x9c,
> function=0x5c73c0 "sysbus_register_withprop") at assert.c:81
> #3 0x000000000052e000 in sysbus_register_withprop (info=<value optimized out>)
> at /src/qemu/hw/sysbus.c:156
> #4 0x000000000041d9c3 in module_call_init (type=<value optimized out>)
> at /src/qemu/module.c:78
> #5 0x0000000000518b64 in main (argc=<value optimized out>,
> argv=<value optimized out>, envp=<value optimized out>)
> at /src/qemu/vl.c:3241
> (gdb) up 3
> #3 0x000000000052e000 in sysbus_register_withprop (info=<value optimized out>)
> at /src/qemu/hw/sysbus.c:156
> 156 assert(info->qdev.size>= sizeof(SysBusDevice));
> (gdb) p *info
> Cannot access memory at address 0x0
> (gdb) p info
> $1 =<value optimized out>
-O1 fixes that.
> (gdb) up
> #4 0x000000000041d9c3 in module_call_init (type=<value optimized out>)
> at /src/qemu/module.c:78
> 78 e->init();
> (gdb) p *e
> $2 = {type = MODULE_INIT_BLOCK,
> init = 0x53cf50<sun4c_intctl_register_devices>, node = {
> tqe_next = 0x1051130, tqe_prev = 0x10510b0}}
static SysBusDeviceInfo sun4c_intctl_info = {
.init = sun4c_intctl_init1,
.qdev.name = "sun4c_intctl",
.qdev.size = sizeof(Sun4c_INTCTLState),
.qdev.vmsd = &vmstate_sun4c_intctl,
.qdev.reset = sun4c_intctl_reset,
};
typedef struct Sun4c_INTCTLState {
SysBusDevice busdev;
...
}
so the code looks fine. Can you dig deeper? Did something stomp on
qdev.size?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2011-08-25 19:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 17:55 [Qemu-devel] PPC* and Sparc32 crash Blue Swirl
2011-08-23 17:59 ` Peter Maydell
2011-08-23 19:19 ` Edgar E. Iglesias
2011-08-24 17:49 ` Blue Swirl
2011-08-24 18:14 ` Edgar E. Iglesias
2011-08-24 18:16 ` Edgar E. Iglesias
2011-08-24 18:39 ` Edgar E. Iglesias
2011-08-24 19:09 ` [Qemu-devel] [PATCH] gt64xxx: fix crash in gt64120_pci_mapping() Avi Kivity
2011-08-24 19:17 ` Edgar E. Iglesias
2011-08-24 17:54 ` [Qemu-devel] PPC* and Sparc32 crash Blue Swirl
2011-08-24 18:05 ` Peter Maydell
2011-08-24 9:41 ` Avi Kivity
2011-08-24 17:48 ` Blue Swirl
2011-08-24 18:20 ` Avi Kivity
2011-08-24 18:40 ` [Qemu-devel] [PATCH] ppc_oldworld, ppc_newworld: fix escc BAR related crash Avi Kivity
2011-08-24 18:43 ` [Qemu-devel] PPC* and Sparc32 crash Avi Kivity
2011-08-24 19:43 ` Blue Swirl
2011-08-24 19:59 ` Avi Kivity
2011-08-24 20:02 ` Blue Swirl
2011-08-25 4:43 ` Avi Kivity
2011-08-25 17:33 ` Blue Swirl
2011-08-25 19:31 ` Avi Kivity [this message]
2011-08-25 20:17 ` Blue Swirl
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=4E56A300.8020805@redhat.com \
--to=avi@redhat.com \
--cc=blauwirbel@gmail.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).