🚀 go-pugleaf

I built Screen 3.2a with the GNU termcap library version 1.1 so I could use
a termcap entry of arbitrary length (the vt320 entry I've written overruns
the system library).  However, I immediately started noticing a strange
problem I hadn't had with v3.2 linked with the system libtermcap.a; at
first it would work fine, but after I had been using the screen for a
couple of days it would tell me that there were no pty's available.  If I
detatched the screen at that point, it would give me the error that it
could not write /etc/utmp as it exited.  When I then resumed, it said it
was unable to find the termcap entry for my terminal.

Using lsof 1.0 to look at the file descriptor table for the server process,
I saw that on first run, and each subsequent resume of that screen session,
the program would open two more links to /etc/termcap.  This overran the
file descriptor table rather rapidly, the way I use screen.

Unfortunately, I can't step through the program to find where the problem
occurs; gdb follows the client when screen forks, and gdb doesn't support
attach/detach on the Sequent Symmetry.

Anyone else had this problem?

--
Jason Merrill