From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Paolo Bonzini <pbonzini@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Strange monitor/stdout issue on qemu-system-sparc/qemu-system-ppc
Date: Tue, 2 Feb 2016 07:47:54 +0000 [thread overview]
Message-ID: <56B05F2A.1080706@ilande.co.uk> (raw)
In-Reply-To: <56AE8352.2040500@redhat.com>
On 31/01/16 21:57, Paolo Bonzini wrote:
> On 31/01/2016 18:54, Peter Maydell wrote:
>> On 31 January 2016 at 17:19, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>> On 31/01/2016 16:54, Mark Cave-Ayland wrote:
>>>> I also notice that with the above commit I lose cycling through history
>>>> in the GTK monitor - even with the multiple echo, instead of the up/down
>>>> arrow keys cycling through the history instead I see the codes ^[[B and
>>>> ^[[A being output to the window instead.
>>>
>>> That is probably me. The echo feature was introduced for QMP, but in
>>> theory it should have been limited to that. I'll check it, thanks.
>>
>> I've also seen echo, but only intermittently...
>
> That smells like uninitialized memory or something like that.
>
> Actually I'm fairly sure I tested "-monitor vc" at least, so perhaps
> it's an interaction between the echo feature and "qemu-char: add logfile
> facility to all chardev backends". Anyway I'll look at it.
Yeah I think you're right. I did a little bit of testing yesterday and
the echo disappeared until I remembered that I'd been testing a
self-built OpenBIOS - and as soon as I reintroduced this option onto the
command line, the echo magically re-appeared.
I can reproduce this consistently under qemu-system-ppc git master like
this:
make distclean
STRIP= './configure' '--target-list=ppc-softmmu'
'--prefix=/home/build/rel-qemu-git' '--enable-gtk' '--disable-pie'
and then specifying a -bios parameter on the command line (even if it is
the same file as that normally used by QEMU):
$ ./qemu-system-ppc -bios ../share/qemu/openbios-ppc
Now try typing into the GTK monitor window and hopefully you should be
able to see the problem.
ATB,
Mark.
next prev parent reply other threads:[~2016-02-02 7:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 15:19 [Qemu-devel] Strange monitor/stdout issue on qemu-system-sparc/qemu-system-ppc Mark Cave-Ayland
2016-01-31 15:34 ` Peter Maydell
2016-01-31 15:54 ` Mark Cave-Ayland
2016-01-31 17:19 ` Paolo Bonzini
2016-01-31 17:54 ` Peter Maydell
2016-01-31 21:57 ` Paolo Bonzini
2016-02-02 7:47 ` Mark Cave-Ayland [this message]
2016-02-08 9:08 ` Paolo Bonzini
2016-02-08 21:44 ` Mark Cave-Ayland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56B05F2A.1080706@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.