On Fri, Jul 07, 2017 at 04:44:53PM +0200, Igor Mammedov wrote: [...] > > 3) Since these checks are done at realize time, we can provide nice > > friendly messages back to the developer to tell them what needs to be fixed > error_set(error_abort, ...) should work nice for fwcfg usecase, > you get error message and a stack trace in core file pointing to a place > of the error.
error_setg(&error_abort, ...) is explicitly discouraged by error_setg() documentation. -- Eduardo
