[libvirt-users] Segfault with ruby-libvirt 0.4.0 and libvirt 1.1.1
Daniel P. Berrange
berrange at redhat.com
Thu Aug 1 14:06:14 UTC 2013
On Thu, Aug 01, 2013 at 03:03:02PM +0200, Bertrand Paquet wrote:
> Hi,
>
> I have upgraded my libvirt version, and I have a crash using ruby-libvirt
> (0.4.0). The same code ruby worked well before upgrade.
>
> ruby(92500,0x107092000) malloc: *** error for object 0x7fdc03ea7658:
> pointer being freed was not allocated
> *** set a breakpoint in malloc_error_break to debug
> Abort trap: 6
>
> I'm under Mac Os, but my colleague is under Linux and have the same problem.
>
> Any idea ?
> Any information to how diagnosis the problem ?
Running the program under valgrind is the best first step to diagnose
memory corruption problems
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
More information about the libvirt-users
mailing list