X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-3.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<4B11E3F6.6050106@cwilson.fastmail.fm>
Date:	Sat, 28 Nov 2009 22:01:10 -0500
From:	Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: [ANNOUNCEMENT] Updated: {terminfo/terminfo-extra/termcap}-5.7_20091114-3
References:	<20091128181347 DOT 2BF44214B54 AT barramail DOT cs DOT umass DOT edu> <4B11DDB7 DOT 3060908 AT cs DOT umass DOT edu>
In-Reply-To:	<4B11DDB7.3060908@cs.umass.edu>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

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?

Thanks for the report.

--
Chuck

--
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

- Raw text -