delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-1.4 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL |
X-Spam-Check-By: | sourceware.org |
MIME-Version: | 1.0 |
In-Reply-To: | <4BFC92B1.2020500@gmail.com> |
References: | <AANLkTimrJ8z8bKwfF-f92TBjradF9pmI9E1l_fs2RoP9 AT mail DOT gmail DOT com> <4BFC92B1 DOT 2020500 AT gmail DOT com> |
Date: | Wed, 26 May 2010 16:24:45 +0200 |
Message-ID: | <AANLkTilNubuGo3WS4weBD3mNEpCW-JwBcN_NFvpRUgCy@mail.gmail.com> |
Subject: | Re: False alarm about exception C0000005 |
From: | Magnus Reftel <magnus DOT reftel AT gmail DOT com> |
To: | cygwin AT cygwin DOT com |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
On 26 May 2010 05:17, Dave Korn <dave DOT korn DOT cygwin AT gmail DOT 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 =A0IT department installed some broken crap on our machines >> again. Sorry for the confusion! > > =A0I had just about reached the same conclusion. =A0The limit to an execu= table > size on my machine was somewhere between 542048077 and 542048589 bytes, a= nd > the only failure mode I observed was a proper error message from bash: > >> $ ./big.exe >> bash: ./big.exe: Cannot allocate memory > > =A0So, I reckon you probably have some interfering BLODA, maybe a DLL tha= t 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |