Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Sat, 21 Feb 2004 16:28:18 +0100
From: Stefan Dalibor <dalibor AT cs DOT fau DOT de>
To: cygwin AT cygwin DOT com
Subject: Re: Zsh crashes on Ctrl-Z with cygwin1.dll snapshot 20040218/20
Message-ID: <20040221152818.GA13501@faui31p.informatik.uni-erlangen.de>
Reply-To: daliboratcsdotfaudotde AT immd3 DOT informatik DOT uni-erlangen DOT de
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i

Please retry with a function to start vim - on my installation

CYGWIN_NT-5.1 SINDBAD 1.5.8s(0.110/4/2) 20040218 17:35:06 i686 unknown unknown Cygwin

it's sufficient to define

function v { vim $*; }

calling this function and then hitting Ctrl-Z crashes zsh reproducibly,
with an otherwise empty home directory (i.e. only the standard shell
and environment settings from Cygwin).

Now it's entirely possible that this is zsh's fault - but I doubt it
seriously.  zsh 4.1.1 is heavily used by thousands of people, and a
bug triggered so easy would certainly have been noticed by someone else 
much earlier (and under other OSes).
And I repeat, the crash doesn't happen with cygwin1.dll 1.5.7.1 (and
the crashes persist with snapshot 20040220).

Do you have any idea how to pinpoint the source of this problem further,
short of building zsh with a debugging malloc (which is something I
probably can't do before 2 or 3 weeks due to lack of time, which would
be much too late for cygwin 1.5.8)?

Please see my other posting about failures to suspend vim and mutt
- this occurs under bash, zsh and pdksh (with the same error message
about handle_threadlist_exception) and as it is also job-control
related, I still suspect a bug lurking in the cygwin DLL here.

Stefan
--
Dr. Stefan Dalibor <dalibor at cs dot fau dot de>

On Thu, Feb 19, 2004 at 10:26:49AM -0800, Peter A. Castro wrote:
> WFM too!
> 
> In fact, I've tested all of the following with zsh:
> 
> 20040213 - works
> 20040214 - works
> 20040215 - can't start zsh (get Appl Error diag box)
> 20040216 - works
> 20040217 - works
> 20040218 - works
> 
> I suspect there is something environmentally wrong with your setup,
> Stefan.  You might try ensuring you don't have any cygwin apps running
> (like inetd, perhaps?).  Use Task Manager to verify that, then start zsh
> with no .z* profiles to ensure you're getting a clean environment.
> 
> > $ uname -a
> > CYGWIN_NT-5.1 fordpc 1.5.8(0.110/4/2) 2004-02-19 09:26 i686 unknown unknown Cygwin
> > $ cygcheck -srv | grep zsh
> > zsh                     4.1.1-2
> > $ sleep 100
> > [^Z here]
> > [1]+  Stopped                 sleep 100
> > $ fg
> > sleep 100
> 
> And, here's my run with the 20040218 snapshot:
> 
> (pcastro AT itdev-nt55)[101] ~ % uname -a
> CYGWIN_NT-4.0 itdev-nt55 1.5.8s(0.110/4/2) 20040218 17:35:06 i686 unknown unknown Cygwin
> (pcastro AT itdev-nt55)[102] ~ % vim
> [Ctrl-Z here]
> zsh: 445 suspended  vim
> (pcastro AT itdev-nt55)[103] ~ % ps -ef
>     UID     PID    PPID TTY     STIME COMMAND
> pcastro      67       1   0  10:17:34 /usr/bin/zsh
> pcastro     445      67   0  10:17:45 /usr/bin/vim
> pcastro     205      67   0  10:17:48 /usr/bin/ps
> (pcastro AT itdev-nt55)[104] ~ % jobs
> [1]  + suspended  vim
> (pcastro AT itdev-nt55)[105] ~ % fg
> [1]  + continued  vim
> (pcastro AT itdev-nt55)[106] ~ %


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/