[Libvir] Core dump while executing virsh in RHEL5 .

Richard W.M. Jones rjones at redhat.com
Mon Oct 15 12:10:45 UTC 2007


Did this problem get fixed while I was away?

What I'm seeing in Veerendra's valgrind log are the following suspicious 
messages, although the line numbers don't correspond to the earlier line 
numbers from gdb:

==17508== Invalid read of size 8
==17508==    at 0x4C5D0BB: doRemoteOpen (remote_internal.c:323)
==17508==    by 0x4C5EABB: remoteNetworkOpen (remote_internal.c:2392)
==17508==    by 0x4C395DA: do_open (libvirt.c:447)
==17508==    by 0x40A80D: main (virsh.c:4507)

     if (uri->user) {
         username = strdup (uri->user);		<--- line 323
         if (!username) goto out_of_memory;
     }


==17508== Invalid write of size 8
==17508==    at 0x4C5D455: doRemoteOpen (remote_internal.c:761)
==17508==    by 0x4C5EABB: remoteNetworkOpen (remote_internal.c:2392)
==17508==    by 0x4C395DA: do_open (libvirt.c:447)
==17508==    by 0x40A80D: main (virsh.c:4507)

     if (query_out) *query_out = NULL;		<-- line 761

As I understand the valgrind message, these indicate that the memory 
being read/written is not valid (ie. outside any allocated malloc block 
or static memory), although I don't understand how those lines could 
generate that error.

(FWIW this is not a core dump that I've ever seen from virsh, but I will 
have a go at seeing if I can reproduce this on my RHEL 5 box later).

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3237 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20071015/374ec48b/attachment-0001.bin>


More information about the libvir-list mailing list