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 22:01:56 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: Outstanding issues with current DLL?
Message-ID: <20010309220156.A799@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <Pine DOT NEB DOT 4 DOT 10 DOT 10103091507340 DOT 8770-100000 AT cesium DOT clock DOT org> <011b01c0a905$b2f2ef90$0200a8c0 AT voyager>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <011b01c0a905$b2f2ef90$0200a8c0@voyager>; from trevorforbes@ozemail.com.au on Sat, Mar 10, 2001 at 11:27:41AM +0930

On Sat, Mar 10, 2001 at 11:27:41AM +0930, Trevor Forbes wrote:
>
>----- Original Message ----- 
>From: "Matt" <matt AT use DOT net>
>To: "Trevor Forbes" <trevorforbes AT ozemail DOT com DOT au>
>Cc: <cygwin-developers AT cygwin DOT com>
>Sent: Saturday, 10 March 2001 8:41 
>Subject: Re: Outstanding issues with current DLL?
>
>
>> > > 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?
>>
>
>No, there seems to be  no pattern to when to it occurs.
>
>Unfortunately, I am at the edge of my knowledge here... 

I know it is a lot of work, but if you could find out exactly when this
started breaking, it would go a long way to figuring out what caused this.

If you are building from CVS you can use the "cvs update -D" command to
revert to a specific point in time.  Otherwise, maybe there are enough
snapshots sitting around to pinpoint the problem.

cgf