Hi,
>>> The previous version of monitor_flush() ignores errors, and everything
>>> works, so doing the same thing here fixes the problem :)
>>
>> No, ignoring errors breaks qmp because the output isn't valid json any
>> more when you cut off something ...
>
> What you mean "when you cut off"? W
On Mon, 25 Mar 2013 08:42:57 +0100
Gerd Hoffmann wrote:
> On 03/22/13 22:39, Luiz Capitulino wrote:
> > On Fri, 22 Mar 2013 16:50:39 -0400
> > Luiz Capitulino wrote:
> >
> >> On Fri, 22 Mar 2013 10:17:58 +0100
> >> KONRAD Frédéric wrote:
> >>
> >>> Hi,
> >>>
> >>> Seems there is an issue with
On 03/22/13 22:39, Luiz Capitulino wrote:
> On Fri, 22 Mar 2013 16:50:39 -0400
> Luiz Capitulino wrote:
>
>> On Fri, 22 Mar 2013 10:17:58 +0100
>> KONRAD Frédéric wrote:
>>
>>> Hi,
>>>
>>> Seems there is an issue with the current git (found by toddf on IRC).
>>>
>>> To reproduce:
>>>
>>> ./qemu-
On Fri, 22 Mar 2013 16:50:39 -0400
Luiz Capitulino wrote:
> On Fri, 22 Mar 2013 10:17:58 +0100
> KONRAD Frédéric wrote:
>
> > Hi,
> >
> > Seems there is an issue with the current git (found by toddf on IRC).
> >
> > To reproduce:
> >
> > ./qemu-system-x86_64 --monitor stdio --nographic
> >
On Fri, 22 Mar 2013 10:17:58 +0100
KONRAD Frédéric wrote:
> Hi,
>
> Seems there is an issue with the current git (found by toddf on IRC).
>
> To reproduce:
>
> ./qemu-system-x86_64 --monitor stdio --nographic
>
> and put "?" it should abort.
>
> Here is the backtrace:
>
> #0 0x7f77cd34
Hi,
Seems there is an issue with the current git (found by toddf on IRC).
To reproduce:
./qemu-system-x86_64 --monitor stdio --nographic
and put "?" it should abort.
Here is the backtrace:
#0 0x7f77cd347935 in raise () from /lib64/libc.so.6
#1 0x7f77cd3490e8 in abort () from /lib64
