This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: Outstanding issues with current DLL?
- To: Trevor Forbes <trevorforbes at ozemail dot com dot au>
- Subject: Re: Outstanding issues with current DLL?
- From: Matt <matt at use dot net>
- Date: Fri, 9 Mar 2001 15:11:44 -0800 (PST)
- cc: cygwin-developers at cygwin dot com
> > 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?