[Top][All Lists]

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

Re: mvwprintw

From: Bob Rossi
Subject: Re: mvwprintw
Date: Thu, 30 Mar 2006 14:29:37 -0500
User-agent: Mutt/1.5.9i

On Thu, Mar 30, 2006 at 01:19:43PM -0500, Bob Rossi wrote:
> On Thu, Mar 30, 2006 at 01:01:13PM -0500, Thomas Dickey wrote:
> > On Thu, 30 Mar 2006, Bob Rossi wrote:
> > 
> > >Can a char string like this:
> > >
> > >$7 = 0x810e700 "(tgdb) b main.c:7                   ..."  where the
> > >string is 81 characters long, and from the '7' up until char 80 they
> > >are all spaces, and char 81 is the NUL char.
> > >
> > >be used with the function like this?
> > > mvwprintw(win, 13, 0, "%s", buffer);
> > >where buffer is the string above.
> > 
> > It looks ok to me - how big is the window?
> It's 60 rows x 80 columns. This is a frustrating bug to find. I've been
> looking at it for an hour and have haven't got anywhere.
> I did notice that my application was sending ^G (bell character) on
> stderr. Would this screw something up?
> I can't figure out why the terminal is printing currupt data when it
> appears that I am passing it a normal string. I ran it through valgrind,
> and it didn't detect any problems. :(

OK, I downloaded the latest ncurses. The problem still exists. However,
when I build ncurses with trace and have NCURSES_TRACE set or not,
everything works fine. This really bothers me.

So, I have ncurses with out trace where it fails to write the screen
properly and I have ncurses_g where it writes to the screen properly.

I don't know if this is my fault or ncurses. Any help?

Bob Rossi

reply via email to

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