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: <010b01c3cd5a$a138c9b0$d6e28351@starfruit>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: <cygwin AT cygwin DOT com>
Subject: 1.5.6-pre: Occasional bad memory accesses within cygwin1.dll
Date: Sun, 28 Dec 2003 15:52:33 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

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.

Debugging suggestions welcome.

Max.


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