From: andrzej zaborowski <balrogg@gmail.com>
To: Bernhard Kauer <kauer@os.inf.tu-dresden.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fix curses update
Date: Thu, 22 Apr 2010 03:27:45 +0200 [thread overview]
Message-ID: <x2ifb249edb1004211827m626658d1p97a275e76b1a7104@mail.gmail.com> (raw)
In-Reply-To: <20100420093835.GC9079@chrom.inf.tu-dresden.de>
Hi,
On 20 April 2010 11:38, Bernhard Kauer <kauer@os.inf.tu-dresden.de> wrote:
> If a terminal is resized or the VGA model issues a full refresh, curses_update()
> is called, which uses mvwaddchnstr() to draw a full line of characters. Unfortunatelly
> this routine expects a null-terminated string and early aborts if a null is present
> in the line.
>
> When booting an OS that zeros the VGA text buffer and later pokes single characters,
> the console output can become unreadable. The attached patch corrects this bug.
I believe this issue has come up before with a similar patch but
someone checked their ncurses and they didn't see the same issue. I
just checked and here mvwaddchnstr() does not expect a null-terminated
string either, but it skips the \0 characters. So probably we should
replace them with spaces or something else, I wouldn't like to
replace a single library call with 80 calls, it's better to go through
the string and replace them, maybe in console_write_ch or somewhere
else.
Cheers
next prev parent reply other threads:[~2010-04-22 1:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 9:38 [Qemu-devel] [PATCH] fix curses update Bernhard Kauer
2010-04-22 1:27 ` andrzej zaborowski [this message]
2010-04-22 14:08 ` Bernhard Kauer
2010-05-03 18:06 ` Anthony Liguori
2010-05-20 20:53 ` [Qemu-devel] [PATCH] fix curses update - v2 Bernhard Kauer
2010-05-21 12:02 ` andrzej zaborowski
2010-05-21 12:43 ` Bernhard Kauer
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=x2ifb249edb1004211827m626658d1p97a275e76b1a7104@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=kauer@os.inf.tu-dresden.de \
--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).