Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <000b01c25b67$a79a46a0$0219a8c0@eric2k>
From: ERIC KRAUSE (ekraus02) <ekraus02 AT baker DOT edu>
To: <Superbiskit AT cox DOT net>
Cc: "Cygwin Discussion" <cygwin AT cygwin DOT com>
References: <3D7A3D30 DOT 2030101 AT cox DOT net> <3D80ABD7 DOT 2090808 AT cox DOT net> <007e01c25a8e$b85ffef0$0219a8c0 AT eric2k> <3D822B23 DOT 6030001 AT cox DOT net>
Subject: Re: [BUG] Intermittant error referencing memory @0x00000010
Date: Fri, 13 Sep 2002 16:53:46 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-15"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700

David A. Cobb writes:
> Thanks, Eric.
>     Uname: CYGWIN_NT 5.0  .... 1.3.12 (0.54.3.2) 2002-07-06 02:16
>     Complete CYGCHECK output appended (.zip)
For some reason the attached file only contained a reiteration of the uname
output.

>     Another datapoint: I tried firing up CYGSERVER and doing the make.
>  Aha!  It ran to completion -- still errors of some sort but none of the
> Win exceptions.
>     That introduced other troubles, I'll post that later and try to keep
> this thread focused.
>     The other thing was terminating all the many aps I have in the
> system tray (   except ZA and my antivirus ) and then keeping my hands
> off while it ran so nothing was perturbing the memory allocations.
>     Having CYGSERVER change things so completely makes me suspect that
> IPC is related to the problem -- I don't know what else changes when the
> server is active; also watching a ProcessExplorer display shows the
> server IPC resources very very active.
>

How far into configure did you get before it crashed the first time?  That
may shed some insight into why it's crashing.  Now your crash was in sh.exe
right?  Cygwin /bin/sh isn't bash--it's the not-so-heavy simpler "ash".

Were you using the "20020131-1" version?  If yes, I'd upgrade "ash" then try
again without cygserver.

---
Eric R. Krause


--
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/