[Top][All Lists]

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

Re: mvwprintw

From: Thomas Dickey
Subject: Re: mvwprintw
Date: Fri, 31 Mar 2006 13:11:49 -0500 (EST)

On Fri, 31 Mar 2006, Bob Rossi wrote:

Also, the trace log kind of makes it look like ncurses is doing the
correct thing. What could be the problem?

At a minimum, what's the next step I can take in order to find the bug?

If it's an ncurses bug, then that should be either repeatable by setting
the same environment, e.g., TERM and the locale stuff, same screen size
and capturing the output using 'script'. It simplifies things to eliminate as many variables (and reduce the logsize, of course).

Occasionally I do find some problem using valgrind, e.g., an uninitialized variable.

If you make the good/bad configurations "identical", and the trace is the
the same on both, but the typescript (from script) is different, that still gives some clues, since the trace doesn't cover everything.

Ultimately all that matters is what goes to the screen. The trace (for the TRACE_UPDATE flag) shows a picture of the before/after each time a refresh is done on a window. While it's useful, that part can make the trace files very large.

sorry (was busy).

Thomas E. Dickey

reply via email to

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