This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: False alarm about exception C0000005


Hi all

I saw this thread when searching for a similar error I'm getting.  Mine is
not with large binaries, but with lots of memory allocations (I'm doing some
processing on a large IC netlist).  When my program reaches around 800 MB of
memory or so it will crash.  I tried to use GDB but it just gave me code
C0000005 and nothing to locate the problem.  I tried to catch a failed
memory allocation using a std::bad_alloc exception but it doesn't seem to
get thrown.

I'm using cygwin 1007.5.0 on Vista 32-bit Enterprise...

Any ideas about this?

Thanks
M


Magnus Reftel wrote:
> 
> 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
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/False-alarm-about-exception-C0000005-tp28667376p28998473.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]