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: <3D80ABD7.2090808@cox.net>
Date: Thu, 12 Sep 2002 10:59:35 -0400
From: "David A. Cobb" <superbiskit AT cox DOT net>
Reply-To: Cygwin Discussion <cygwin AT cygwin DOT com>
Organization: CoxNet User
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020905
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Cygwin Discussion <cygwin AT cygwin DOT com>
Subject: Re: [BUG] Intermittant error referencing memory @0x00000010
X-Priority: 1 (highest)
References: <3D7A3D30 DOT 2030101 AT cox DOT net>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

OK.  No-one picked up on this before.  Since then I did a search on the 
archive.  This may be related to the "fork(): ... Resource temporarily 
unavailable" -
because I see that too but thought it was a secondary symptom.

A couple of questions, maybe slightly smarter than before:
    I currently have error_start=dumper.exe, and I do not see dumper 
bringing up a console window in these errors.  It seems windows is 
dealing with the error itself and perhaps the Cygwin DLL never gets to 
see it (?).  If that is the case, how can I do JIT debugging?  It really 
needs to be an error_start, because of the unpredictable character 
during a /long/ make.
    So that a problem in the DLL doesn't also bite GDB, would y'all 
expect the MinGW GDB port to work?

    Most of the discussion I spotted was last year!  Has there been any 
progress in this?  Should I try re-basing, and if so, which dll's should 
be rebased?

OH YEAH!  Windoz2000pro, 192Meg real memory, latest of everything Cygwin.

Thanks,

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)"
>
> 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?
>
> Today, tried the same and configure ran like a charm.  However, "make 
> bootstrap" incurred the same
> 'memory at 0x00000010 could not be written' and 'App failed to 
> initialize' errors in /usr/bin.gcc.exe
>
> There seems no simple way to predict when this will happen, so I 
> imagine any debug/strace output would be huge.
> Is this a known bug?
>

-- 
David A. Cobb, Software Engineer, Public Access Advocate
"By God's Grace I am a Christian man, by my actions a great sinner." -- The Way of a Pilgrim; R. M. French, tr.
Life is too short to tolerate crappy software.
.



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