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: <007e01c25a8e$b85ffef0$0219a8c0@eric2k>
From: ERIC KRAUSE (ekraus02) <ekraus02 AT baker DOT edu>
To: "Cygwin Discussion" <cygwin AT cygwin DOT com>
References: <3D7A3D30 DOT 2030101 AT cox DOT net> <3D80ABD7 DOT 2090808 AT cox DOT net>
Subject: Re: [BUG] Intermittant error referencing memory @0x00000010
Date: Thu, 12 Sep 2002 15:00:53 -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:
> On 09/07/2002, David A. Cobb wrote:
>
> > Trying to do a bootstrap build of gcc-3.2-1, first cat.exe signalled
> > 'cat.exe the instruction at 0x077f8ed61 referenced memory at
> > 0x0000010. The memory could not be "written"'
> > followed by "Application failed to initialize (0xC0000142)"

0xC0000142 looks like a Windows exception code.  Keep in mind on Win9x
you'll get the infamous page fault error and no Application failed to
initialize msg.

> > Retry, got the same error but in "sh.exe instruction at 0x77f8ed61" --
> > HEY! that's strange - the same instruction address.
> > must be in a dll, yes?

Correct.  Apps don't have such high addresses, for future reference--they're
normally based at 0x400000 (so they can run on Windows 9x).

objdump on cygwin1.dll shows me one DLL dependency: kernel32.dll.  objdump
on kernel32 shows base is 0x77e80000.  But objdump on kernel32.dll also
shows it depends upon ntdll.dll.  objdump on ntdll.dll shows base is
0x77f80000, and has no DLL dependencies.  The code triggering the crash is
inside ntdll.dll.

Since kernel32.dll and ntdll.dll are *likely* OK (you never know M$, though,
but let's assume their code is kosher anyhow), AND considering that 3
SEPARATE .exe's caused the SAME problem, it looks like the only suspect left
is cygwin1.dll.

Are you using the latest Cygwin DLL version?  You can find out just what
that version number is from the output of "uname -a"; it's right after your
hostname.

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