X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20091002110141.GB685@calimero.vinschen.de> 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> Date: Fri, 2 Oct 2009 12:12:02 +0100 Message-ID: <416096c60910020412r542534d4s865cf03a10bc33b5@mail.gmail.com> Subject: Re: snapshot 20091002 and xterm crash From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 2009/10/2 Corinna Vinschen: > > [Ping Yaakov] > > > On Oct =C2=A02 09:04, Marco Atzeri wrote: >> Hi, >> >> xterm abort when run in snapshot 20091002 >> reverting to 20090924 solve the issue. >> >> Run as: >> DISPLAY=3D127.0.0.1:0.0 xterm =C2=A0-ls /usr/bin/bash.exe > > I can reproduce that. =C2=A0I 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. =C2=A0In 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. =C2=A0If 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 > However, starting xterm works if you set, for instance, the environment > variable $LANG to "C.UTF-8". =C2=A0This works: > > =C2=A0DISPLAY=3D127.0.0.1:0.0 LANG=3DC.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 = ... Andy -- 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