X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Fri, 2 Oct 2009 13:24:48 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: snapshot 20091002 and xterm crash
Message-ID: <20091002112448.GD685@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <66412 DOT 78339 DOT qm AT web25503 DOT mail DOT ukl DOT yahoo DOT com> <20091002110141 DOT GB685 AT calimero DOT vinschen DOT de> <416096c60910020412r542534d4s865cf03a10bc33b5 AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <416096c60910020412r542534d4s865cf03a10bc33b5@mail.gmail.com>
User-Agent: Mutt/1.5.19 (2009-02-20)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Oct  2 12:12, Andy Koppe wrote:
> 2009/10/2 Corinna Vinschen:
> >
> > [Ping Yaakov]
> >
> >
> > On Oct  2 09:04, Marco Atzeri wrote:
> >> Hi,
> >>
> >> xterm abort when run in snapshot 20091002
> >> reverting to 20090924 solve the issue.
> >>
> >> Run as:
> >> DISPLAY=127.0.0.1:0.0 xterm  -ls /usr/bin/bash.exe
> >
> > I can reproduce that.  I found the problem and it's really puzzeling.
> >
> > In the snapshot 2009-10-02, the default charset for the "C" locale is
> > set to UTF-8 for the application.  In 2009-09-24, it was only using
> > UTF-8 for filenames and other system objects by default.
> >
> > When starting xterm with no locale environment variable set, it fails
> > to start.  If you're quick enough, you can read a message along the
> > lines of "Cannot allocate pty: No such file ..."
> 
> That could be a luit problem:
> 
> http://www.mail-archive.com/cygwin-xfree AT cygwin DOT com/msg19129.html

Uh, I see.  Thanks for the pointer.

> > However, starting xterm works if you set, for instance, the environment
> > variable $LANG to "C.UTF-8".  This works:
> >
> >  DISPLAY=127.0.0.1:0.0 LANG=C.UTF-8 xterm
> >
> > However, even though newlib handles "UTF8" same as "UTF-8", it's
> > apparently not the same for xterm.
> 
> Random guess: xterm recognises "UTF-8" in $LANG and concludes that no
> translation is needed. It doesn't recognise "UTF8" (without the
> hyphen), nor does it know that plain "C" now implies "UTF-8", hence it
> invokes "luit" to do the translation, which fails for the reason
> above.
> 
> No idea why the luit problem didn't show up more prominently before though ...

Indeed.

So it's not xterm, it's luit.  That explains the weird strace output
which shows that, for some reason, xterm tries to open /dev/ptyxx,
which isn't available on Cygwin.

I guess I can drop the ashen look from my face again.  Not being able to
use UTF-8 by default would have rendered a good amount of work of the
last couple of days useless.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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