[Top][All Lists]

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

Re: bug: ncurses + slackware 10.0, 10.1

From: Thomas Dickey
Subject: Re: bug: ncurses + slackware 10.0, 10.1
Date: Fri, 18 Mar 2005 09:54:50 -0500 (EST)

On Fri, 18 Mar 2005, Frank Heckenbach wrote:

Thomas Dickey wrote:

On Thu, 17 Mar 2005, Russell Whitaker wrote:

Program below illustrates a bug: lower case a,  lower case f thru z,
and number 0 are printed with graphic characters. This bug did not
appear in earlier versions of slackware.

I don't have Slackware 10.0 or 10.1; a quick try at testing this with
Debian isn't working out, since the Debian package apparently doesn't
build any of the units - just the compiler.

Please use the option `--automake' when calling gpc, then it will
build the units together with the program.

thanks (I did read the info page, but there are many options).

Also, you might have to remove the `FrameWin' unit (it's not a
standard unit, and the call to it is already commented out).

However, if it's an ncurses change (nothing offhand occurs to me, reading
the example), one could use ltrace to get a reasonable idea of the calls
that are being made in ncurses (not 100%, since some of the interface may
modify the WINDOW struct directly, but probably good enough to see this
sort of problem).

I don't have Slackware 10.x here either, and the program works
correctly for me. Unless you can reproduce a bug with the hints
above, I guess I'll have to check it with the respective ncurses
version to find out if it's a GPC or CRT bug (which would be my
responsibility ...)

ok (I'll try this when I get home).  My ncurses shared libraries are
current, but I do have static libraries for different versions, against
which I may be able to test (though I'm not sure how to tell gpc to do

Russ, which ncurses version is it that you have? Look in
/usr/include/ncurses.h for:


The last I knew, Slackware is using 5.4 (release/no patches).

Thomas E. Dickey

reply via email to

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