qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] How do I disable -curses mode?
Date: Thu, 8 Oct 2009 03:03:25 -0500	[thread overview]
Message-ID: <200910080303.26027.rob@landley.net> (raw)

I'm running qemu -nographic from a script, booting up a linux -kernel with a 
serial console and driving it via "expect" to feed data to its stdin and parse 
its output.

This worked fine under 0.10.0, but under 0.11.0 it craps curses escape 
sequences all over the place, ala:

Type exit when done.
/ #        #
^[[24;5R/ # # Show free space
/ # df
^[[24;13R^[[24;5RFilesystem           1K-blocks      Used Available Use% 
Mounted on

This confuses "expect" because it doesn't get the lines it's looking for, 
those escape sequences can show up in the middle of a line.

I'm already saying -nographic, which vl.c seems to imply is a different code 
path from -curses, yet it's spitting all this extra stuff to the output anyway.

If I recompile telling ./configure to --disable-curses the problem goes away, 
but I can't tell distro maintainers to do that and I can't always build qemu 
from source.

In this instance neither qemu's stdin nor its stdout is a tty, so you'd think 
the curses code would NOTICE.  (It's not that hard to call ttyname() on stdin 
and see if you get a null pointer, is it?)

Rob 
-- 
Latency is more important than throughput. It's that simple. - Linus Torvalds

             reply	other threads:[~2009-10-08  8:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08  8:03 Rob Landley [this message]
2009-10-09  5:15 ` [Qemu-devel] How do I disable -curses mode? Rob Landley

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=200910080303.26027.rob@landley.net \
    --to=rob@landley.net \
    --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).