On Fri, Dec 14, 2012 at 11:18:18AM +0100, Igor Mammedov wrote:
> On Wed, 12 Dec 2012 16:16:23 -0200
> Eduardo Habkost wrote:
>
> > Instead of forcing the caller to guess what went wrong while creating
> > the CPU object, return error information in a Error argument.
> >
> > Also, as cpu_x86_crea
On Wed, 12 Dec 2012 16:16:23 -0200
Eduardo Habkost wrote:
> Instead of forcing the caller to guess what went wrong while creating
> the CPU object, return error information in a Error argument.
>
> Also, as cpu_x86_create() won't print error messages itself anymore,
> change cpu_x86_init() to pr
Instead of forcing the caller to guess what went wrong while creating
the CPU object, return error information in a Error argument.
Also, as cpu_x86_create() won't print error messages itself anymore,
change cpu_x86_init() to print any error returned by cpu_x86_create()
or cpu_x86_realize().
Sign
Instead of forcing the caller to guess what went wrong while creating
the CPU object, return error information in a Error argument.
Also, as cpu_x86_create() won't print error messages itself anymore,
change cpu_x86_init() to print any error returned by cpu_x86_create()
or cpu_x86_realize().
Sign
