Luiz Capitulino <lcapitul...@redhat.com> writes: > Ideally, Monitor code should report an error only once and > return the error information up the call chain. > > To assure that this happens as expected and that no error is > lost, we have an assert() in qemu_error_internal(). > > However, we still have not fully converted handlers using > monitor_printf() to report errors. As there can be multiple > monitor_printf() calls on an error, the assertion is easily > triggered when debugging is enabled; and we will get a memory > leak if it's not. > > The solution to this problem is to allow multiple faults by only > reporting the first one, and to release the additional error objects.
I want this badly. [...]
