False alarm about exception C0000005

[Magnus Reftel]

On 26 May 2010 05:17, Dave Korn <dave.korn.cygwin@gmail.com> wrote:
> On 25/05/2010 12:47, Magnus Reftel wrote:
>> Hi all,
>>
>> I discovered that the problem does not only affect Cygwin. It was just
>> that I did not have any large binaries outside cygwin. Large
>> executables built using VS Express also crash with the same exception.
>> I guess the  IT department installed some broken crap on our machines
>> again. Sorry for the confusion!
>
>  I had just about reached the same conclusion.  The limit to an executable
> size on my machine was somewhere between 542048077 and 542048589 bytes, and
> the only failure mode I observed was a proper error message from bash:
>
>> $ ./big.exe
>> bash: ./big.exe: Cannot allocate memory
>
>  So, I reckon you probably have some interfering BLODA, maybe a DLL that is
> injected into all processes and tries to allocate some memory at startup or
> something like that and doesn't handle a failure well.

That seems to be correct. In the failing case (when compiled with VS),
the VS debugger lists ntdll.dll and kernel32.dll being loaded before
the crash, and when the executable does not crash, sysfer.dll and
msvcr100d.dll are also loaded. sysfer is a Symantec DLL. Should have
guessed it...

Anyway, thanks for looking at this and sorry to have wasted your time!

Best Regards
Magnus Reftel

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple