Re: qemu-kvm-1.2.0: double free or corruption

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Nov 19, 2012 at 8:56 AM, Nikola Ciprich
<nikola.ciprich@xxxxxxxxxxx> wrote:
> on one of our servers, windows 2008 KVM suddenly crashed. I see following
> in libvirt log:
>
> *** glibc detected *** /usr/bin/qemu-kvm: double free or corruption (!prev): 0x00007fc634008cd0 ***
> ======= Backtrace: =========
> /lib64/libc.so.6(+0x75916)[0x7fc9026f4916]
> /lib64/libc.so.6(+0x78443)[0x7fc9026f7443]
> /usr/bin/qemu-kvm(+0x1faeb1)[0x7fc907187eb1]
> /usr/bin/qemu-kvm(+0x1f0e1a)[0x7fc90717de1a]
> /usr/bin/qemu-kvm(+0x1fb681)[0x7fc907188681]
> /usr/bin/qemu-kvm(+0xed6a7)[0x7fc90707a6a7]
> /usr/bin/qemu-kvm(+0x195c31)[0x7fc907122c31]
> /usr/bin/qemu-kvm(main+0x106c)[0x7fc90711e5fc]
> /lib64/libc.so.6(__libc_start_main+0xfd)[0x7fc90269dcdd]
> /usr/bin/qemu-kvm(+0x749f9)[0x7fc9070019f9]
[...]
> I guess this is not of much use, since I didn't have debuginfo package installed
> in time of crash. Is it possible to obtain more debuginfo after I installed it?
> Is there something else I should check to find where the problem could be?

No problem, you can still resolve symbols afterwards.  Download the
debuginfo package and use something along the lines of:
$ addr2line -e /path/to/debug-executable 0x1faeb1 0x1f0e1a 0x1fb681
0xed6a7 0x195c31

It's important to fetch the debuginfo package for the exact same
version of the qemu RPM you were running.

Stefan
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux