Re: Zsh crashes on Ctrl-Z with cygwin1.dll snapshot 20040218/20

Re: Zsh crashes on Ctrl-Z with cygwin1.dll snapshot 20040218/20

[Stefan Dalibor]

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@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@itdev-nt55)[102] ~ % vim
> [Ctrl-Z here]
> zsh: 445 suspended  vim
> (pcastro@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@itdev-nt55)[104] ~ % jobs
> [1]  + suspended  vim
> (pcastro@itdev-nt55)[105] ~ % fg
> [1]  + continued  vim
> (pcastro@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/

Re: Zsh crashes on Ctrl-Z with cygwin1.dll snapshot 20040218/20

[Christopher Faylor]

On Sat, Feb 21, 2004 at 04:28:18PM +0100, Stefan Dalibor wrote:
>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 $*; }

Nope.  Still works fine.

I assume that, since you're telling people to define a function, vim
suspends correctly when not used with a function?  That's odd.  It
makes no sense at all that having bash, pdksh, or zsh go through an
extra level of command translation would make vim unsuspendable.

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

How does malloc enter into it?  I don't see anything pointing to malloc
here.

cgf

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

Re: Zsh crashes on Ctrl-Z with cygwin1.dll snapshot 20040218/20 - solved with 20040221

[Stefan Dalibor]

On Sat, Feb 21, 2004 at 03:48:43PM -0500, Christopher Faylor wrote:
> On Sat, Feb 21, 2004 at 04:28:18PM +0100, Stefan Dalibor wrote:
> >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 $*; }
> 
> Nope.  Still works fine.

Strange - if I have no personale customizations left, what could be
the difference that makes the bug reproducable on my system and
irreproducable on yours?  Should I mail the complete output of
`cygcheck -c' on my machine, the list of XP patches installed or
something similar?

Anyway, your patch for the crash of mutt when being suspended fixes
the zsh problem, too - it's gone after upgrading to snapshot 20040221!

> >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)?
> 
> How does malloc enter into it?  I don't see anything pointing to malloc
> here.

I was just guessing for the usual suspects - if it's not the cygwin DLL,
a memory management bug in zsh triggered by the latest changes in the
Cygwin environment seemed like a plausible candidate to me.

As the crashes are fixed by snapshot 20040221, should I investigate
further (in case another bug is lurking behind the scenes), or can
we consider this file closed?

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

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

Re: Zsh crashes on Ctrl-Z with cygwin1.dll snapshot 20040218/20 - solved with 20040221

[Christopher Faylor]

On Sun, Feb 22, 2004 at 02:23:50AM +0100, Stefan Dalibor wrote:
>As the crashes are fixed by snapshot 20040221, should I investigate
>further (in case another bug is lurking behind the scenes), or can
>we consider this file closed?

Thanks for confirming that this is fixed.  I was worried that there
was another problem lurking with vim.

If all of the SEGVs are fixed then I think there's no reason to look
further.

cgf

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