This is the mail archive of the
mailing list for the Cygwin project.
1.5.6-pre: Occasional bad memory accesses within cygwin1.dll
- From: "Max Bowsher" <maxb at ukf dot net>
- To: <cygwin at cygwin dot com>
- Date: Sun, 28 Dec 2003 15:52:33 -0000
- Subject: 1.5.6-pre: Occasional bad memory accesses within cygwin1.dll
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.
Debugging suggestions welcome.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html