Message-ID: <4B11E904.6070806@cs.umass.edu>
Date: Sat, 28 Nov 2009 22:22:44 -0500
From: Eliot Moss <moss@cs.umass.edu>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: {terminfo/terminfo-extra/termcap}-5.7_20091114-3
References: <20091128181347.2BF44214B54@barramail.cs.umass.edu> <4B11DDB7.3060908@cs.umass.edu> <4B11E3F6.6050106@cwilson.fastmail.fm>
In-Reply-To: <4B11E3F6.6050106@cwilson.fastmail.fm>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Charles Wilson wrote:
> Eliot Moss wrote:
>> The new termcap causes my xterm to segmentation fault.
>> When I back out just the termcap line of this update
>> in cygwin setup, xterm fires up fine.
> 
> Sigh. I think I know what the problem is. The fix is simple, but...
> 
> Some of the terminfo entries require more than 1KB to represent in
> termcap format.  I was using 'tic -T' to "go ahead and use it anyway".
> Looks like I can't get away with that. I'll investigate and roll a new
> release.
> 
> BTW, how are you invoking xterm? What shell?

It is started as part of my .xinitrc, so bash I guess. I could not
see the actual error there. I see the segmentation fault then I
try starting an xterm from an rxvt window (running bash). This is
with X started. With the working termcap, saying "xterm" in the
rxvt window creates an xterm window within the X window, as expected.

Best wishes -- EM

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple