This is the mail archive of the
cygwin-xfree
mailing list for the Cygwin XFree86 project.
Re: Xterm hangs with latest Cygwin (-62?)
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-xfree at cygwin dot com
- Date: Mon, 5 Oct 2009 10:20:21 +0200
- Subject: Re: Xterm hangs with latest Cygwin (-62?)
- References: <4AC8CFC4.7060105@alum.mit.edu> <806a89db0910041044n10e2c6d9i5aa62b9043652c42@mail.gmail.com> <20091004195204.GA1826@calimero.vinschen.de> <4AC92A72.1040002@alum.mit.edu>
- Reply-to: cygwin-xfree at cygwin dot com
- Reply-to: cygwin-xfree at cygwin dot com
On Oct 4 17:06, Jim Reisert AD1C wrote:
> On 10/4/2009 1:52 PM, Corinna Vinschen wrote:
>
>> Stracing shows that luit is called with `luit -argv0 -tcsh', but nowhere
>> in the strace tcsh is actually started. Rather, it looks like luit
>> starts /bin/sh with argv[0] set to -tcsh instead.
>
> Interesting. When I was experimenting with -62, I noticed several tcsh.exe
> processes in the Windows task manager. Maybe they're sort of starting, but
> don't get connected to the xterm somehow?
Neither the strace, nor Task Manager show any tcsh process in my case.
There's a difference, though, when starting xterm via the `run -p xterm
-ls' shortcut. With Cygwin -61, xterm just starts tcsh and it works,
with Cygwin -62, xterm tries to start the shell via luit, and that
fails. If luit is missing on the system (renamed), xterm starts with
a message "Can't execvp /usr/bin/luit: No such file or directory", and
then starts tcsh just fine afterwards.
Since there's no difference otherwise, it's not clear to me why this
occurs. In both cases the locale is set to the default "C" locale.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/