Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: 20 Jul 2001 16:30:58 -0400
Message-ID: <20010720203058.19025.qmail@lizard.curl.com>
From: Jonathan Kamens <jik AT curl DOT com>
To: cygwin AT cygwin DOT com
Subject: CVS repository appears to be unstable; any ETA for fix?

It looks to me like the code in the Cygwin CVS repository is unstable
right now.  I just updated from the repository and recompiled, and I'm
getting various kinds of errors like this one:

  16175 [main] gawk 379 fhandler_base::fork_fixup: /dev/tty0 - Win32 error 6, handle output_handle<0x440>

and this one:

  91463 [main] sh 365 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
Exception: STATUS_ACCESS_VIOLATION at eip=61046871
eax=00000001 ebx=0241E414 ecx=00000000 edx=0241AAFC esi=0A0113D0 edi=00000001
ebp=0241E524 esp=0241D6F0 program=c:\cygwin\bin\sh.exe
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame     Function  Args
0241E524  61046871  (000003E8, 00000220, 1A0201C0, 000001B6)
0241F574  610471F4  (1A020A18, 000003E8, 00000220, 1A0201C0)
0241F5B4  6104737C  (40000000, 1A020A18, 000003E8, 00000220)
0241F5F4  610473F9  (40000000, 1A020A18, 000001B6, 61010969)
0241F644  61010988  (1A02FC50, 00000601, 000001B6, 50040161)
0241F684  610125A3  (1A02FC50, 0241F6B4, 00000601, 000001B6)
0241F9F4  61012482  (1A02FC50, 0A015040, 00000601, 000001B6)
0241FA34  6105665E  (0A015040, 00000601, 000001B6, 00405F59)
0241FA54  6107DC6A  (0A015040, 00000601, 000001B6, 6107B6FE)
0241FA84  0040C6E2  (0A010980, 0241FAD4, 00000000, 610552B5)
0241FAE4  0040C5B5  (0A010980, 00000000, 0241FC64, 00402ED9)
0241FC64  00402EEA  (0A0109AC, 00000001, 00000000, 6107B6FE)
0241FC94  00401D74  (0A0109AC, 00000001, 00000000, 00401D74)
0241FCD4  0040234D  (0A010788, 00000000, 0241FD04, 0040AEC1)
0241FD04  00401D61  (0A010788, 00000000, 0241FD44, 0040A1BA)
0241FD34  00401CC9  (0A0109BC, 00000000, 0241FD64, 0040A111)
End of stack trace (more stack frames may be present)

I'm wondering if (a) you know about these problems and (b) you have an
ETA for when they might be fixed, so I can decide whether I need to
backport the debugging code (I'm trying to track down a Cygwin bug)
I've got in my sandbo to an earlier, more stable version of the DLL
source code.

Thanks,

  jik

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/