Path: utzoo!attcan!uunet!cs.utexas.edu!csd4.milw.wisc.edu!uxc.cso.uiuc.edu!uxc.cso.uiuc.edu!ux1.cso.uiuc.edu!osiris.cso.uiuc.edu!dpgerdes
From: dpgerdes@osiris.cso.uiuc.edu
Newsgroups: comp.unix.microport
Subject: Re: Curses bug in V/AT 2.4 - what was i
Message-ID: <42700022@osiris.cso.uiuc.edu>
Date: 16 Jun 89 15:02:00 GMT
References: <353@osc.COM>
Lines: 29
Nf-ID: #R:osc.COM:353:osiris.cso.uiuc.edu:42700022:000:886
Nf-From: osiris.cso.uiuc.edu!dpgerdes    Jun 16 10:02:00 1989


/* Written  5:19 pm  Jun 13, 1989 by rp@osc.COM in osiris.cso.uiuc.edu:comp.unix.microport */
>/* ---------- "Curses bug in V/AT 2.4 - what was i" ---------- */
>Hi,
>	I remember a couple of months ago that there is a bug in the
>curses support under System V/AT ver. 2.4.  Does anybody remember what it
>was ??  Also, if anybody has a fix for it that would be appreciated.  Please
>either post or e-mail directly to me.
>

    Don't know about the specific bug you are talking about, but the
code below will die on just about any SysV out there.  The problem, I believe, 
is that endwin() does not release allocated memory.

#include <curses.h>
main ()
{
    register int i = 0 ;
    while  (++i)
    {
	printf ("Executing loop number: %d\r", i);
	initscr ();
	endwin ();
    }
}

On V/386 after about 90 some loops I get:

 Sorry, I don't know anything about your 'vt100' terminal.