Re: [PATCH] hw/m68k/mcf5206: Replace remaining hw_error()s by qemu_log_mask()

2020-06-11 Thread Philippe Mathieu-Daudé
On 6/11/20 7:58 AM, Thomas Huth wrote: > hw_error() dumps the CPU state and exits QEMU. This is ok during initial > code development (to see where the guest code is currently executing), > but it is certainly not the desired behavior that we want to present to > normal users, and it can also cause

Re: [PATCH] hw/m68k/mcf5206: Replace remaining hw_error()s by qemu_log_mask()

2020-06-11 Thread Laurent Vivier
Le 11/06/2020 à 07:58, Thomas Huth a écrit : > hw_error() dumps the CPU state and exits QEMU. This is ok during initial > code development (to see where the guest code is currently executing), > but it is certainly not the desired behavior that we want to present to > normal users, and it can also

[PATCH] hw/m68k/mcf5206: Replace remaining hw_error()s by qemu_log_mask()

2020-06-10 Thread Thomas Huth
hw_error() dumps the CPU state and exits QEMU. This is ok during initial code development (to see where the guest code is currently executing), but it is certainly not the desired behavior that we want to present to normal users, and it can also cause trouble when e.g. fuzzing devices. Thus let's r