[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Monitor and serial output window broken with SDL2

From: BALATON Zoltan
Subject: Re: [Qemu-devel] Monitor and serial output window broken with SDL2
Date: Mon, 17 Dec 2018 22:57:14 +0100 (CET)
User-agent: Alpine 2.21.9999 (BSF 287 2018-06-16)

On Mon, 17 Dec 2018, Daniel P. Berrangé wrote:
On Mon, Dec 17, 2018 at 03:56:49PM +0100, BALATON Zoltan wrote:
On Wed, 21 Mar 2018, BALATON Zoltan wrote:
On Wed, 21 Mar 2018, Gerd Hoffmann wrote:
while the serial output seems to be behind the monitor output in the window
opening with Ctrl+Alt+2 and flashes when I type in this window. (This
doesn't seem to happen with qemu-system-x86_64, maybe that's why
it was not catched.)

Doesn't reproduce too.  It's also not clear why x86_64 should behave
different that ppc.  There is no arch-specific code ui/, so there should
be no difference, exept for hardware like paralle ports which are not
supported by all machine types.

Any chance you have tested an old ppc binary?

Not likely because I did make distclean and a clean build before testing
to avoid any possible mismatch. It still does not work for me though.

I still have this problem after updating everything on my machine, latest
QEMU and SDL 2.0.9 so it's not likely to be a bug in some external
component. If I just start qemu-system-ppc (compiled with --disable-gtk) and
try to open monitor console with Ctrl-Alt-2 I see QEMU monitor but when I
type in this window the serial output window contents flash in this window.
At the same time the window that opens for Ctrl-Alt-3 which should have the
serial output is empty. It looks like an index may be off somewhere or
window contents are not associated with the right window but I have no idea
where to look for it. Can you reproduce it now and do you have any idea what
could cause this?

Could you share an example command line which can be used to reproduce
the problem.

As I wrote above ust "qemu-system-ppc" without any options reproduces the problem here.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]