This is the mail archive of the
mailing list for the Cygwin project.
Re: 1.5.6-pre: Occasional bad memory accesses within cygwin1.dll
- From: Nicholas Wourms <nwourms at netscape dot net>
- To: cygwin at cygwin dot com
- Date: Sun, 28 Dec 2003 12:36:07 -0500
- Subject: Re: 1.5.6-pre: Occasional bad memory accesses within cygwin1.dll
- References: <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
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
Also, are you having any trouble with lynx?
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html