Re: [Libvir] virt-install : *** glibc detected *** /usr/bin/python: free(): invalid pointer *** ***

[Richard W.M. Jones]

suyash jape wrote:

Hi all

 I am getting the following output when i try to use virt-install

[EMAIL PROTECTED] virt-install

======= Backtrace: =========
/lib/i686/nosegneg/libc.so.6[0x2f89b1]
/lib/i686/nosegneg/libc.so.6(cfree+0x90)[0x2fc060]
/usr/lib/libvirt.so.0[0xb2885e]
/usr/lib/libvirt.so.0[0xb2a07b]
/usr/lib/libvirt.so.0[0xb019d3]

.
.
.
.

b7f25000-b7fa9000 rw-p b7f25000 00:00 0
b7fb4000-b7fb5000 rw-p b7fb4000 00:00 0
bff2a000-bff4a000 rw-p bff2a000 00:00 0          [stack]
Aborted

My package versions :

[EMAIL PROTECTED] ~]# rpm -qa|grep libvirt
libvirt-0.3.3-1.fc7
libvirt-python-0.3.3-1.fc7

[EMAIL PROTECTED] ~]# uname -a


[EMAIL PROTECTED] ~]# rpm -qa|grep xen
xen-libs-3.1.0-6.fc7
xen-devel-3.1.0-6.fc7
xen-3.1.0-6.fc7
kernel-xen-2.6.20-2936.fc7
kernel-xen-devel-2.6.20-2936.fc7

I have attached the full back trace if anyone is interested
Any suggestions ?

*** glibc detected *** /usr/bin/python: free(): invalid pointer: 0x08bea0a0 *** /usr/lib/python2.5/site-packages/libvirtmod.so(libvirt_virConnectOpen+0x66)[0xf09ce6] b7d25000-b7f25000 r--p 00000000 fd:00 312403 /usr/lib/locale/locale-archive Linux localhost.localdomain 2.6.20-2936.fc7xen #1 SMP Fri Sep 21 12:07:35 EDT 2007 i686 i686 i386 GNU/Linux

# rpm -qa | grep xen
kernel-xen-2.6.21-2949.fc8
kernel-xen-2.6.21-2942.fc8
kernel-xen-devel-2.6.21-2942.fc8
xen-libs-3.1.0-12.fc8
xen-debuginfo-3.1.0-5.fc8
xen-devel-3.1.0-12.fc8
xen-3.1.0-12.fc8
kernel-xen-devel-2.6.21-2949.fc8

(FYI, virt-install runs fine on the above machine).



./autogen.sh --enable-debug=yes --prefix=$HOME/local
make all install
LD_LIBRARY_PATH=$HOME/local/lib virt-install

Rich.

--
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903

I'd definitely be interested in the full stacktrace. Also does this occur with the latest releases (ie. enable the development repo): If you want to pursue this further, then compiling libvirt with the --enable-debug=yes option produces a lot of interesting debugging output, and will allow us to see what actual libvirt calls are being made, plus arguments.

smime.p7s
Description: S/MIME Cryptographic Signature

--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list