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
Date: Mon, 29 Dec 2003 22:37:11 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.5.6-pre: Occasional bad memory accesses within cygwin1.dll
Message-ID: <20031230033711.GA20304@redhat.com>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <010b01c3cd5a$a138c9b0$d6e28351 AT starfruit>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <010b01c3cd5a$a138c9b0$d6e28351@starfruit>
User-Agent: Mutt/1.4.1i
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

On Sun, Dec 28, 2003 at 03:52:33PM -0000, 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

This isn't too useful, unfortunately.  The line numbers are an artifact
of the fact that there is no STABS information in the generated asm in
'sigfe.s'.  Can you get an assembly listing of the lines around this
instruction?

>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

I fixed a problem like this a while ago.  It's difficult to see how this
case could occur unless you are using an old version of sigproc.cc, in
particular, the no_signals_available macro sounds like it isn't
up-to-date.

cgf

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