Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
Date:	Fri, 9 Mar 2001 15:11:44 -0800 (PST)
From:	Matt <matt AT use DOT net>
X-Sender:	matt AT cesium DOT clock DOT org
To:	Trevor Forbes <trevorforbes AT ozemail DOT com DOT au>
cc:	cygwin-developers AT cygwin DOT com
Subject:	Re: Outstanding issues with current DLL?
In-Reply-To:	<006001c0a8eb$e3b3db90$0200a8c0@voyager>
Message-ID:	<Pine.NEB.4.10.10103091507340.8770-100000@cesium.clock.org>
MIME-Version:	1.0

> > What kind of random failures are you seeing?  Hanging?  SIGSEGVs?
> 
> sed and sh give stackdump with no info (well, nothing I can see)
> 
> For example :
> 
> Exception: STATUS_ACCESS_VIOLATION at eip=00000000
> eax=00000000 ebx=00000007 ecx=61084EEC edx=00000000 esi=6108D15C
> edi=6108D164
> ebp=0241F9F8 esp=0241FE94 program=f:\Cygwin\bin\sed.exe
> cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
> Stack trace:
> Frame     Function  Args
> End of stack trace


ack. EIP being NULL isn't good, isn't that usually indicative that
something is smashing the stack?

is this reproducible at all?

- Raw text -