On Tue, Mar 10, 2009 at 10:16:26AM +0100, Daniel Veillard wrote:
On Fri, Mar 06, 2009 at 05:21:25PM +0000, Nuno Fernandes wrote:
Starting install... *** glibc detected *** /usr/bin/python: free(): invalid next size (fast): 0x0936a1b8 *** ======= Backtrace: ========= /lib/i686/nosegneg/libc.so.6[0x1e0906] /lib/i686/nosegneg/libc.so.6(cfree+0x90)[0x1e3e30] /usr/lib/libvirt.so.0(virFree+0x24)[0x8eb4e4] /usr/lib/libvirt.so.0[0x94793c] /usr/lib/libvirt.so.0[0x93abf1] /usr/lib/libvirt.so.0(virDomainLookupByUUID+0xb7)[0x8fda77] /usr/lib/libvirt.so.0(virDomainLookupByUUIDString+0x17f)[0x8ffbaf] /usr/lib/python2.4/site- packages/libvirtmod.so(libvirt_virDomainLookupByUUIDString+0x6d)[0xfa349d]
Yes I'm seeing this too on 0.6.1 on RHEL-5.3, I'm trying to chase it down, it's a bit hard to find out where the memory corruption occurs.
I guess the key is to run under GDB with -debuginfo installed so we get a complete stack trace - the 2 missing symbols between virDomainLookupByUUID and virFree will be the key to finding this... Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|