delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2016/08/12/04:00:46

X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
:list-unsubscribe:list-subscribe:list-archive:list-post
:list-help:sender:date:from:to:subject:message-id:reply-to
:references:mime-version:content-type:in-reply-to; q=dns; s=
default; b=V+M0idly2BdzExkmlJD59zanyRiWEJl45MpgnbOgpC8GMf+WqjD5o
IAGE9yvz6RfdjqV662CmfIFAX376NwSC1CuDacr269YO+us6u+1RKXFbWgedOoXt
xoFrXOkYsz1CIEjcIiu1FZE5sgtqnbIVP3tEDkl2roZW5OXEPn7xJo=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
:list-unsubscribe:list-subscribe:list-archive:list-post
:list-help:sender:date:from:to:subject:message-id:reply-to
:references:mime-version:content-type:in-reply-to; s=default;
bh=6huzRhnsZayADySqQrYChfo1+7U=; b=tHatfIRJDDRE5K1GX7SVKavPP/bA
BWa6NwMSbKhy0xaB6/Z26e+x5UOlyjJ9d4B/3ZGL2S3bSIjZKJsTTYn/832n3ygx
L7AIoF6gzlKJPBQeKIDo4wJlSW0OjZg0gv/udDVguadSOQr/GK9V1eKYuJ/fYLvx
7GeMm0EVb0/1n4E=
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-95.1 required=5.0 tests=AWL,BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_BRBL_LASTEXT,RCVD_IN_PBL,RCVD_IN_SORBS_DUL,RDNS_DYNAMIC autolearn=ham version=3.3.2 spammy=narrow, H*MI:sk:a479a3a, H*i:sk:a479a3a, H*f:sk:a479a3a
X-HELO: calimero.vinschen.de
Date: Fri, 12 Aug 2016 10:00:04 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: tcsh version 6.19.00-3 hangs on exit
Message-ID: <20160812080004.66zdbxdzjlcmnxak@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <a479a3ac-dfb1-44eb-3ad6-1ec24b753994 AT gmail DOT com>
MIME-Version: 1.0
In-Reply-To: <a479a3ac-dfb1-44eb-3ad6-1ec24b753994@gmail.com>
User-Agent: Mutt/1.6.2-neo (2016-07-23)

--y7wl2wlcfs7m52xa
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Thomas,

On Aug 11 16:36, Thomas Taylor wrote:
> I really appreciate your looking into this problem.  I use the Cygwin64
> Terminal icon to create one or more windows.  I set my login shell to
> /bin/tcsh in /etc/passwd.  As you suggested, I deleted ~/.logout, and do =
not
> have an /etc/csh.logout.  I also deleted ~/.login, and reduced my (option=
al)
> ~/.cshrc to only the following two lines:
>=20
>     set history=3D100
>     set savehist=3D($history merge lock)
>=20
> In this case (if I understand correctly) tcsh first sources /etc/csh.cshr=
c,
> then ~/.cshrc, then /etc/csh.login.  The files /etc/csh.cshrc and
> /etc/csh.login are as downloaded from one of the Cygwin x86_64 mirror sit=
es,
> and are unchanged by me; only the optional file ~/.cshrc (above) has been
> added by me.  Unfortunately, all mintty windows hang upon exit, and each
> must be killed (along with its associated tcsh) using the Windows Task
> Manager.  C-Shell scripts started from the command line also hang upon ex=
it
> (unless their first line contains the fast startup flag "-f"), and must be
> killed with Control-C.  The mintty windows and the C-Shell scripts do not
> hang if the third word "lock" is removed from the setting of savehist in
> ~/.cshrc.  I would like to use "lock" for the reasons mentioned in the tc=
sh
> man pages.  Things seemed to work fine until a couple of weeks ago, when I
> updated my Cygwin system.

Ok, I'm not using "lock" myself, but even with "lock" I can't reproduce
your observation, neither interactive, nor running a script.

I wonder if this a BLODA problem, perhaps, see
https://cygwin.com/faq/faq.html#faq.using.bloda

If that doesn't help, we might need more debugging on your side.  For
instance, what you could do is to start a CMD shell and start tcsh from
there via strace, i. e.:

  C:\cygwin\bin> strace -o tcsh.trace tcsh -l

This is much slower than usual so be patient.  Provoke the hang.  Then
kill tcsh from task manager.  Send the tcsh.trace file as attachment to
this list.  It might help to narrow down the problem.


Thanks,
Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--y7wl2wlcfs7m52xa
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXrYIEAAoJEPU2Bp2uRE+gBOIQAKVsCZbMie5eJvtS6/u/9Srr
wlObgaQlwZ4BiBfTKAAmvu9PeyFL0EQtd7BPtp4FO0Rh784JdEn9XdpRWdC9taxp
avVesN30IdwlAPzlu9RdAAP6inxMnGmgJGaOmfc5+Arg6DJAyglkI2YGA8b0oez4
p9oA2XRWgWspz+MM8QpsN21EcUwQi9VptB2nUNGu/pOK1PehQTkclOaEDHI6m0e0
xX/MjwXS2AaH05CKWdFh+XsRYBpk1klAHXKH7PazF1zKZqR6n7uxDARUNmPoG3YN
eepHjVX2hN2dePHK8z1NkWXA/GrVbtyfz53bBXXXEUsFyolP5CPfQa6X5LchMh8H
V+jrLTPv5JxlIiJ0CMMP7Qn0UYfJ6/CyWyDYN7HwKpKNcRQg0kjvpz1G84mDwzRy
Y+BF2CZ+B7f5NnWDHe8sIwFf/UXE0p/APY2D1mIQj9tZR6Ts956IOsaqG46u9jQ1
fqDBg6f02fHTfuyzk+P5222tc1E8DuwZppnp4+ufFCe/7MBMfAPQn2ndzLWoxfvI
Wf/cTBToRZ9PGkf5dhNIaqQhCdrW57RiCbHVnjuoX1X8XwWT8QiF79BrPnG4Dx0P
GyFtG6zpr2LCYg1WqpnfVF/bsPL3R0xS5fqoJVOb06U6sJ0r5BWDYjC45pZDE5FO
YP7mxMOraucYocjcsPMU
=HSYw
-----END PGP SIGNATURE-----

--y7wl2wlcfs7m52xa--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019