* Christoph Hellwig <h...@lst.de> [2011-08-22 10:16]:
> On Mon, Aug 22, 2011 at 09:59:16AM -0500, Ryan Harper wrote:
> > * Christoph Hellwig <h...@lst.de> [2011-08-21 17:27]:
> > > changes since V1:
> > > - rebase to apply against the current qemu.git tree
> >
> >
> > Testing on tip + this series with:
> >
> > ./configure --enable-debug --enable-kvm --enable-io-thread
> > --target-list=x86_64-softmmu
>
> That is about the same config that I run.
>
> > [New Thread 0x7ffff4f27700 (LWP 18033)]
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x00000000004200c1 in bdrv_acct_done (bs=0x12310b0, cookie=0x1c69f50) at
> > /root/git/qemu/block_int.h:239
> > 239 bs->nr_bytes[cookie->type] += cookie->bytes;
>
> I can't see how this can result in a segfault, unless we get a corrupted
> cookie. Can you print what cookie->type is from gdb?
(gdb) frame 0
#0 0x00000000004200c1 in bdrv_acct_done (bs=0x12310b0, cookie=0x1c68810) at
/root/git/qemu/block_int.h:239 239 bs->nr_bytes[cookie->type] +=
cookie->bytes;
(gdb) p *cookie
$3 = {bytes = 72057589759737855, start_time_ns = 72057589759737855, type =
16777215}
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ry...@us.ibm.com
