[Top][All Lists]

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

Re: mvwprintw

From: Bob Rossi
Subject: Re: mvwprintw
Date: Mon, 3 Apr 2006 14:19:18 -0400
User-agent: Mutt/1.5.9i

> >Hi Thomas,
> >
> >Sorry I haven't got to the bottom of this yet. Hopefully I'll find the
> >problem today. Since the debug doesn't seem to be helping to much here,
> >what's the lowest level function I should be debugging to determine why
> >my screen is getting corrupted?
> hmm - go back to my last explanation.  The screen is being corrupted 
> because either ncurses or some other code is writing bad data.  If it is 
> ncurses, you should be able to see it by tracing the low-level function
> PutAttrChar(), which is actually doing the output to the screen.  The 
> trace you sent should have showed PutAttrChar(), but did not.
> I'd see why it did not, and fix that (perhaps I misread the trace-level).
> Then see if PutAttrChar() is getting bad data, or making it bad - there's
> one call to PUTC() in tty_update.c which is doing the work.

OK, I'll do that. As a side note, is ncurses smart enough to only output
to the terminal the info that has changed, instead of the whole screen?

I'm not sure if you looked at the strace I sent in. Oddly enough, it
picks up on the strange char's being written to stdout. The confusing 
thing to me is the fact that I know more is written to the terminal than 
what is displayed in the strace output. I can't figure out why it's not
in there. Attached is the output.

Bob Rossi

Attachment: strace.fd1.out
Description: Text document

reply via email to

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