Re: Ensure errors are reported against virConnect object

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

 



On Wed, Oct 25, 2006 at 07:20:30PM +0100, Daniel P. Berrange wrote:
> In xend_internal.c there are a large number of places where errors are being
> reported without supplying an associated virConnectPtr object. So for example
> when calling virDomainCreateLinux, some errors get associated with the
> connection object, while others get attached to the global error object.
> The attached patch fixes up all places in xend_internal.c which have an
> virConnectPtr object available to always pass this object into the the
> error reporting funcs.

  Yup makes perfect sense. A lot of this was the result of plugging
existing code from Anthony, so the data was not passed down,

  thanks !

Daniel

-- 
Red Hat Virtualization group http://redhat.com/virtualization/
Daniel Veillard      | virtualization library  http://libvirt.org/
veillard@xxxxxxxxxx  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine  http://rpmfind.net/


[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]