Problem with Curses

[Klaus Schilling]

kjwolf at online.de (Klaus-Juergen Wolf) writes:

> Klaus-Juergen Wolf <kjwolf at online.de> wrote:
>  > (Python 1.5.2 on FreeBSD 3.2-RELEASE (i386))
> 
>  > I found that (after having compiled Python with cursesmodule.c -

Andrich's curses support is more complete, particularly suited for
x/openpg compliant curses. It turns to be very useful to replace it.

>  > testall.py succeeds) the following program gives a segmentation
>  > fault:
> 
> As it appears,
> 
> -*-
> import curses
> 
> curses.initscr()
> curses.endwin()
> -*-
> 
> alone does exactly the same. I've tested it in debugging environment,
> where it doesn't happen, and I've checked the cursesmodule code, and I
> still have no idea why this happens. (Inconsistency? But where?)
> 
> Stack trace says that it happens when the first actual write call to
> libtermcap takes place.

So curses on that platform still needs to be linked to libtermcap?
> 
> The problem occurs under Solaris in the same way, while Linux doesn't
> seem to know anything of it.

Using libtermcap on those systems? Linux usually uses terminfo which is
already burried in the ncurses stuff. Solaris might use sun curses.

Btw why is there no direct termcap support for python? 
Perl has Term::Cap , which doesn't even require the termcap library,
just the termcap data file (e.g. /etc/termcap). 
Would it be very hard to provide? 

Klaus Schilling