aboutsummaryrefslogtreecommitdiff
path: root/bsd-user
diff options
context:
space:
mode:
authorLuiz Capitulino <lcapitulino@redhat.com>2010-02-08 17:01:29 -0200
committerAnthony Liguori <aliguori@us.ibm.com>2010-02-10 13:46:17 -0600
commit27a749fb733dc64b7a215998be7f228a09bb27a7 (patch)
treefc4e56507e348227a6081a86f61a3f012887f8ba /bsd-user
parentba14414174b72fa231997243a9650feaa520d054 (diff)
downloadqemu-27a749fb733dc64b7a215998be7f228a09bb27a7.zip
qemu-27a749fb733dc64b7a215998be7f228a09bb27a7.tar.gz
qemu-27a749fb733dc64b7a215998be7f228a09bb27a7.tar.bz2
QError: Don't abort on multiple faults
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. A better mechanism to report multiple errors to programmers is underway. Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'bsd-user')
0 files changed, 0 insertions, 0 deletions