On Thu, Feb 02, 2017 at 11:26:16AM +, Wei Liu wrote:
> On Mon, Jan 30, 2017 at 03:33:18PM +0100, Fatih Acar wrote:
> > libxl_domain_build_info_dispose is not resetting the type field to
> > LIBXL_DOMAIN_TYPE_INVALID.
> > Instead, it is memseting the struct to 0 thus when
> > libxl_domain_buil
On Mon, Jan 30, 2017 at 03:33:18PM +0100, Fatih Acar wrote:
> libxl_domain_build_info_dispose is not resetting the type field to
> LIBXL_DOMAIN_TYPE_INVALID.
> Instead, it is memseting the struct to 0 thus when
> libxl_domain_build_info_init_type is called
> after a dispose on the same struct, an
libxl_domain_build_info_dispose is not resetting the type field to
LIBXL_DOMAIN_TYPE_INVALID.
Instead, it is memseting the struct to 0 thus when
libxl_domain_build_info_init_type is called
after a dispose on the same struct, an assertion is triggered because type !=
LIBXL_DOMAIN_TYPE_INVALID.
Ca
