Eric Blake writes:
> On 07/23/2015 08:01 AM, Markus Armbruster wrote:
>> This is particularly useful when we abort in error_propagate(),
>> because there the stack backtrace doesn't lead to where the error was
>> created. Looks like this:
>>
>> Unexpected error in parse_block_error_action()
On 07/23/15 16:47, Eric Blake wrote:
> On 07/23/2015 08:01 AM, Markus Armbruster wrote:
>> This is particularly useful when we abort in error_propagate(),
>> because there the stack backtrace doesn't lead to where the error was
>> created. Looks like this:
>>
>> Unexpected error in parse_block
On 07/23/2015 08:01 AM, Markus Armbruster wrote:
> This is particularly useful when we abort in error_propagate(),
> because there the stack backtrace doesn't lead to where the error was
> created. Looks like this:
>
> Unexpected error in parse_block_error_action() at
> /work/armbru/qemu/blo
This is particularly useful when we abort in error_propagate(),
because there the stack backtrace doesn't lead to where the error was
created. Looks like this:
Unexpected error in parse_block_error_action() at
/work/armbru/qemu/blockdev.c:322:
qemu-system-x86_64: -drive if=none,werror=fo
