[opensource-dev] Windows surprise build error

[Nicky Perian]

Cwgwin build problems occur when using an updated Windows 10 and an Updated
Cygwin64.
Below are the error messages and corrections.
This problem started on Sunday November 29, 2015.
Luck was on my side as I had a Win7 system that had recently been updated
to Win10 and was still in the rollback
period. Rolled it back and no build problems. Updated to win10 and probelm
returned. Used dumpbin abd editbin
as shown below and the problem is no more.
2>------ Build started: Project: lscript_compile, Configuration: Release
Win32 ------
12>  Building Custom Rule
C:/Users/Bill/kokua/indra/lscript/lscript_compile/CMakeLists.txt
12>  CMake does not need to re-run because
C:\Users\Bill\kokua\build-vc120\lscript\lscript_compile\CMakeFiles\generate.stamp
is up-to-date.
12>  Generating indra.l.cpp
12>        0 [main] flex 5736 C:\cygwin64\bin\flex.exe: *** fatal error in
forked process - fork: can't reserve memory for parent stack 0x600000 -
0x800000, (child has 0x400000 - 0x600000), Win32 error 487
12>      782 [main] flex 5736 cygwin_exception::open_stackdumpfile: Dumping
stack trace to flex.exe.stackdump
11>  httprequest.cpp
11>  httpresponse.cpp
11>  _httplibcurl.cpp
6>  llfindlocale.cpp
6>  llfixedbuffer.cpp
12>        0 [main] flex 1068 fork: child -1 - forked process 5736 died
unexpectedly, retry 0, exit code 0x100, errno 11
12>  flex: fork failed
6>  llformat.cpp
12>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.target
C:\cygwin64\bin>dumpbin /headers flex.exe
C:\cygwin64\bin>editbin /STACK:0x20000 flex.exe
Above corrected for flex.
Then, bison gave the following.
>  Generating indra.y.cpp, indra.y.hpp
3>C:/Users/Bill/kokua/indra/lscript/lscript_compile/indra.y : warning : 88
reduce/reduce conflicts [-Wconflicts-rr]
3>        0 [main] bison 7264 C:\cygwin64\bin\bison.exe: *** fatal error in
forked process - fork: can't reserve memory for parent stack 0x600000 -
0x800000, (child has 0x400000 - 0x600000), Win32 error 487
3>     3749 [main] bison 7264 cygwin_exception::open_stackdumpfile: Dumping
stack trace to bison.exe.stackdump
4>------ Build started: Project: copy_w_viewer_manifest, Configuration:
Release Win32 ------
3>        1 [main] bison 10736 fork: child -1 - forked process 7264 died
unexpectedly, retry 0, exit code 0x100, errno 11
3>  /usr/bin/bison: m4 subprocess failed: Resource temporarily unavailable
C:\cygwin64\bin>dumpbin /headers bison.exe
C:\cygwin64\bin>editbin /STACK:0x20000 bison.exe


Building is complete.


On Tue, Dec 1, 2015 at 10:02 PM, Nicky Perian <nickyperian at gmail.com> wrote:

> What a fragile pile of dung. A time bomb. Guess this is a good lesson to
> not update or upgrade a
> working dev machine.
> https://cygwin.com/faq/faq.html#faq.using.bloda
>
> *4.45.*
>
> What applications have been found to interfere with Cygwin?
>
> From time to time, people have reported strange failures and problems in
> Cygwin and Cygwin packages that seem to have no rational explanation. Among
> the most common symptoms they report are fork failures, memory leaks, and
> file access denied problems. These problems, when they have been traced,
> often appear to be caused by interference from other software installed on
> the same PC. Security software, in particular, such as anti-virus,
> anti-spyware, and firewall applications, often implements its functions by
> installing hooks into various parts of the system, including both the
> Explorer shell and the underlying kernel. Sometimes these hooks are not
> implemented in an entirely transparent fashion, and cause changes in the
> behaviour which affect the operation of other programs, such as Cygwin.
>
> Among the software that has been found to cause difficulties are:
>
>    -
>
>    Sonic Solutions burning software containing DLA component (when DLA
>    disabled)
>    -
>
>    Norton/McAfee/Symantec antivirus or antispyware
>    -
>
>    Logitech webcam software with "Logitech process monitor" service
>    -
>
>    Kerio, Agnitum or ZoneAlarm Personal Firewall
>    -
>
>    Iolo System Mechanic/AntiVirus/Firewall
>    -
>
>    LanDesk
>    -
>
>    Windows Defender
>    -
>
>    Various programs by Wave Systems Corp using wxvault.dll, including
>    Embassy Trust Suite and Embassy Security Center
>    -
>
>    NOD32 Antivirus
>    -
>
>    ByteMobile laptop optimization client
>    -
>
>    Earthlink Total-Access
>    -
>
>    Spybot S&D TeaTimer
>    -
>
>    AR Soft RAM Disk
>    -
>
>    ATI Catalyst (some versions)
>    -
>
>    NVIDIA GeForce (some versions)
>    -
>
>    Windows LiveOneCare
>    -
>
>    Webroot Spy Sweeper with Antivirus
>    -
>
>    COMODO Firewall Pro
>    -
>
>    PC Tools Spyware Doctor
>    -
>
>    Avira AntiVir
>    -
>
>    Panda Internet Security
>    -
>
>    BitDefender
>    -
>
>    Google Desktop
>    -
>
>    Sophos Anti-Virus 7
>    -
>
>    Bufferzone from Trustware
>    -
>
>    Lenovo IPS Core Service (ipssvc)
>    -
>
>    Lenovo RapidBoot Shield
>    -
>
>    Credant Guardian Shield
>    -
>
>    AVAST (disable FILESYSTEM and BEHAVIOR realtime shields)
>    -
>
>    Citrix Metaframe Presentation Server/XenApp (see Citrix Support page
>    <http://support.citrix.com/article/CTX107825>)
>    -
>
>    Lavasoft Web Companion
>
> Sometimes these problems can be worked around, by temporarily or partially
> disabling the offending software. For instance, it may be possible to
> disable on-access scanning in your antivirus, or configure it to ignore
> files under the Cygwin installation root. Often, unfortunately, this is not
> possible; even disabling the software may not work, since many applications
> that hook the operating system leave their hooks installed when disabled,
> and simply set them into what is intended to be a completely transparent
> pass-through mode. Sometimes this pass-through is not as transparent as all
> that, and the hooks still interfere with Cygwin; in these cases, it may be
> necessary to uninstall the software altogether to restore normal operation.
>
> Some of the symptoms you may experience are:
>
>    -
>
>    Random fork() failures.
>
>    Caused by hook DLLs that load themselves into every process in the
>    system. POSIX fork() semantics require that the memory map of the child
>    process must be an exact duplicate of the parent process' layout. If one of
>    these DLLs loads itself at a different base address in the child's memory
>    space as compared to the address it was loaded at in the parent, it can end
>    up taking the space that belonged to a different DLL in the parent. When
>    Cygwin can't load the original DLL at that same address in the child, the
>    fork() call has to fail.
>    -
>
>    File access problems.
>
>    Some programs (e.g., virus scanners with on-access scanning) scan or
>    otherwise operate on every file accessed by all the other software running
>    on your computer. In some cases they may retain an open handle on the file
>    even after the software that is really using the file has closed it. This
>    has been known to cause operations such as deletes, renames and moves to
>    fail with access denied errors. In extreme cases it has been known for
>    scanners to leak file handles, leading to kernel memory starvation.
>    -
>
>    Networking issues
>
>    Firewall software sometimes gets a bit funny about Cygwin. It's not
>    currently understood why; Cygwin only uses the standard Winsock2 API, but
>    perhaps in some less-commonly used fashion that doesn't get as well tested
>    by the publishers of firewalls. Symptoms include mysterious failures to
>    connect, or corruption of network data being sent or received.
>    -
>
>    Memory and/or handle leaks
>
>    Some applications that hook into the Windows operating system exhibit
>    bugs when interacting with Cygwin that cause them to leak allocated memory
>    or other system resources. Symptoms include complaints about out-of-memory
>    errors and even virtual memory exhaustion dialog boxes from the O/S; it is
>    often possible to see the excess memory allocation using a tool such as
>    Task Manager or Sysinternals' Process Explorer, although interpreting the
>    statistics they present is not always straightforward owing to
>    complications such as virtual memory paging and file caching.
>
> ​
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/opensource-dev/attachments/20151203/7eadae61/attachment.htm