qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Monitor and serial output window broken with SDL2
Date: Tue, 18 Dec 2018 06:54:08 +0100	[thread overview]
Message-ID: <20181218055408.6yxxumlhw56vzzus@sirius.home.kraxel.org> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1812172255250.25213@zero.eik.bme.hu>

  Hi,

> > > > > 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.
> > > > While
> > > 
> > > 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.

Still doesn't reproduce, using "qemu-system-ppc -display sdl".  x86_64
is fine too.  Also using SDL 2.0.9.

"struct sdl2_console" holds the per-window state, you could try to
sprinkle some debug printfs (or add trace points) to sdl2_window_create,
sdl2_redraw, ...

HTH,
  Gerd

  reply	other threads:[~2018-12-18  5:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 22:43 [Qemu-devel] Monitor and serial output window broken with SDL2 BALATON Zoltan
2018-03-21 14:06 ` Gerd Hoffmann
2018-03-21 17:25   ` BALATON Zoltan
2018-12-17 14:56     ` BALATON Zoltan
2018-12-17 15:00       ` Daniel P. Berrangé
2018-12-17 21:57         ` BALATON Zoltan
2018-12-18  5:54           ` Gerd Hoffmann [this message]
2018-12-18 10:58           ` Daniel P. Berrangé
2018-12-18 10:54       ` Mark Cave-Ayland
2018-12-18 11:16         ` Daniel P. Berrangé
2018-12-18 13:11           ` BALATON Zoltan
2018-12-18 13:27             ` Daniel P. Berrangé
2018-12-18 19:05               ` BALATON Zoltan
2018-12-19  9:53                 ` Daniel P. Berrangé
2018-12-19 18:11                   ` BALATON Zoltan
2018-12-20  5:42                     ` Gerd Hoffmann
2018-12-20 11:18                       ` BALATON Zoltan

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=20181218055408.6yxxumlhw56vzzus@sirius.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=balaton@eik.bme.hu \
    --cc=berrange@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).