On 15/08/2018 16:19, Markus Armbruster wrote:
> When read() from the qtest socket or the QMP socket fails or EOFs, we
> report "Broken pipe" and exit(1). This commonly happens when QEMU
> crashes. It also happens when QEMU refuses to run because the test
> passed it bad arguments. Sadly, we negl
Philippe Mathieu-Daudé writes:
> On 08/15/2018 11:19 AM, Markus Armbruster wrote:
>> When read() from the qtest socket or the QMP socket fails or EOFs, we
>> report "Broken pipe" and exit(1). This commonly happens when QEMU
>> crashes. It also happens when QEMU refuses to run because the test
>
On 08/15/2018 09:19 AM, Markus Armbruster wrote:
When read() from the qtest socket or the QMP socket fails or EOFs, we
report "Broken pipe" and exit(1). This commonly happens when QEMU
crashes. It also happens when QEMU refuses to run because the test
passed it bad arguments. Sadly, we neglect
On 08/15/2018 11:19 AM, Markus Armbruster wrote:
> When read() from the qtest socket or the QMP socket fails or EOFs, we
> report "Broken pipe" and exit(1). This commonly happens when QEMU
> crashes. It also happens when QEMU refuses to run because the test
> passed it bad arguments. Sadly, we n
When read() from the qtest socket or the QMP socket fails or EOFs, we
report "Broken pipe" and exit(1). This commonly happens when QEMU
crashes. It also happens when QEMU refuses to run because the test
passed it bad arguments. Sadly, we neglect to report either.
Improve this by calling abort()
