Problem with suspending processes under bash, pdksh and zsh with cygwin1.dll snapshot 20040218/20

[Stefan Dalibor <dalibor at cs dot fau dot de>]

Hi,
I upgraded to cygwin1.dll snapshot version 20040218 and 2004020 (due to
problems with zsh and cygwin-1.5.7.1):

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

Now I find that I can suspend a process running vim only once by Ctrl-Z
- after restarting the process, hitting Ctrl-Z any more won't work.
The terminal window flickers for a moment, but the editor is not
suspended.
Suspending a lynx process more than once works fine, while suspending
mutt results in a crash:

4 [sig] mutt 1152 handle_threadlist_exception: handle_threadlist_exception
called with threadlist_ix -1
Segmentation fault (core dumped)

with stackdump:

Exception: STATUS_ACCESS_VIOLATION at eip=61025D4B
eax=00000011 ebx=00000000 ecx=006DEB6C edx=61025650 esi=006DEBDC edi=61025650
ebp=006DE864 esp=006DE53C program=C:\cygwin\bin\mutt.exe
cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
Stack trace:
Frame     Function  Args
006DE864  61025D4B  (00000000, 00000012, 00000000, 00000000)
006DEB94  61026784  (00000750, 006DEBDC, 000000A4, 006DEBC8)
006DF0A4  6108D45E  (610F0774, 00000000, 006DF0C4, 006DF0FC)
006DF0C4  610030A6  (610F0774, 006DF0FC, 61003040, 000FF6BD)
006DF0F4  61003DE4  (00000000, 00000000, 00000000, 00000000)
006DFFA4  61003D9A  (00000000, 00000000, 00000000, 00000000)
End of stack trace

This is with an empty home directory, i.e. only the standard shell and
terminal settings from Cygwin, and it happens with bash, pdksh and zsh
(where the latter crashes also with the same error message when
suspending vim if the editor is called from within a shell function,
please see my other posting).

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/