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
To: cygwin AT cygwin DOT com
From: Nicholas Wourms <nwourms AT netscape DOT net>
Subject: Re: 1.5.6-pre: Occasional bad memory accesses within cygwin1.dll
Date: Sun, 28 Dec 2003 12:36:07 -0500
Lines: 39
Message-ID: <3FEF1487.2080908@netscape.net>
References: <010b01c3cd5a$a138c9b0$d6e28351 AT starfruit>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet AT sea DOT gmane DOT org
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
In-Reply-To: <010b01c3cd5a$a138c9b0$d6e28351@starfruit>

Max Bowsher wrote:

> I installed a self-built cygwin HEAD version - mostly it works fine, but it
> causes odd failures during builds (speculation: race when many processes
> being created and destroyed?)
> 
> The most common failure is a Windows error box:
> 
> The instruction at "0x6108621a" references memory at "0x610030b0". The
> memory could not be written.
> 
> (These addresses are constant.)
> 
> $ addr2line -e /bin/cygwin1.dll 0x6108621a 0x610030b0
> .../src/winsup/cygwin/shm.cc:331
> .../src/winsup/cygwin/cygthread.cc:34
> 
> The errors are usually in sed, grep, or dirname.
> 
> This is sometimes accompanied by this error on the console:
> 
> 4 [proc] sh 1160 sig_send: error sending signal 20 to pid 1160, pipe handle
> 0xFFFFFFFF, Win32 error 6
> 
> Less common failures include shell scripts receiving terminating with a
> "Hangup" message, or locking up entirely.
> 

I've seen this while running recursive `make`'s.  Have you tried running 
configure or make from within gdb?  I've found that doing that actually 
seems to prevent the races which you describe, however it does cause 
make to screwup the subdir entry order.  As for the locking up, a big 
ditto there.

Also, are you having any trouble with lynx?

Cheers,
Nicholas



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/