X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.4 required=5.0 tests=AWL,BAYES_00
X-Spam-Check-By:	sourceware.org
Message-ID:	<4B13DEE7.3040206@cs.umass.edu>
Date:	Mon, 30 Nov 2009 10:04:07 -0500
From:	Eliot Moss <moss AT cs DOT umass DOT edu>
User-Agent:	Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	My original report of xterm breaking with the new termcap
X-IsSubscribed:	yes
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

--------------030600070000060702020902
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

... as Corinna requested :-) ...

Fairly easy to follow forward to the maintainer's diagnosis
that a termcap entry is too big, which causes this failure.

Cheers -- Eliot

--------------030600070000060702020902
Content-Type: message/rfc822;
 name="Re: [ANNOUNCEMENT] Updated: {terminfo/terminfo-extra/termcap}-5.7_20091114-3.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename*0="Re: [ANNOUNCEMENT] Updated: {terminfo/terminfo-extra/termcap";
 filename*1="}-5.7_20091114-3.eml"

Return-Path: <moss AT cs DOT umass DOT edu>
Delivered-To: moss AT csmail DOT cs DOT umass DOT edu
Received: from mail.cs.umass.edu (loki.cs.umass.edu [128.119.240.93])
	by csmail.cs.umass.edu (Postfix) with ESMTPS id 262D1300000CB8917B
	for <moss AT csmail DOT cs DOT umass DOT edu>; Sat, 28 Nov 2009 21:34:31 -0500 (EST)
Received: from csmail.cs.umass.edu (csmail.cs.umass.edu [128.119.240.177])
	by mail.cs.umass.edu (8.13.8/8.13.1) with ESMTP id nAT2YUaM027180
	for <moss AT cs DOT umass DOT edu>; Sat, 28 Nov 2009 21:34:30 -0500
Received: from [192.168.0.7] (c-71-233-223-205.hsd1.ma.comcast.net [71.233.223.205])
	by csmail.cs.umass.edu (Postfix) with ESMTPSA id D0BF8380000CB89128;
	Sat, 28 Nov 2009 21:34:30 -0500 (EST)
Message-ID: <4B11DDB7 DOT 3060908 AT cs DOT umass DOT edu>
Date: Sat, 28 Nov 2009 21:34:31 -0500
From: Eliot Moss <moss AT cs DOT umass DOT edu>
Organization: UMass Computer Science
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
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>
In-Reply-To: <20091128181347 DOT 2BF44214B54 AT barramail DOT cs DOT umass DOT edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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.

xterm -v prints Cygwin 6.8.99.903(250), which shows
up as 250-1 in setup.

The libtermcap.a that works is labeled 20050421-1;
the new one that causes the seg fault is labeled
5.7_20091114-12.

I am running cygwin 1.7.0-67.

terminfo is the new one (5.7_20091114-12).
terminfo0 is 5.5_2006104-11.

Has something changed in a way that requires xterm
to be rebuilt to work?

As you point out, it should probably use terminfo
instead, but that is kind of out of my hands as an
xterm user ...

Best wishes -- Eliot Moss


--------------030600070000060702020902
Content-Type: text/plain; charset=us-ascii

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

- Raw text -