Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <025101c1a1c5$ba4b2280$0200a8c0@lifelesswks> From: "Robert Collins" To: References: <022e01c1a1b6$da6c6060$0200a8c0 AT lifelesswks> Subject: Re: setup crashing (attn Corinna) Date: Mon, 21 Jan 2002 02:18:33 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 20 Jan 2002 15:20:30.0149 (UTC) FILETIME=[FEF9AF50:01C1A1C5] Oh, nearly forgot, theres' a minor w32api change as well needed to build this. Rob === ----- Original Message ----- From: "Robert Collins" To: Sent: Monday, January 21, 2002 12:32 AM Subject: setup crashing (attn Corinna) > Corinna, > > Something seriously funny was going on in the C++/C runtime interaction. > Rather than try and explain it, I've linked in a recent version of Doug > Lea's malloc, which also had a couple of quirks, that I've (apparently) > fixed. > > If you could see if the problematic site still affects you that would be > great. (It doesn't affect me anymore). > > I did find some oddities, but fixing them didn't resolve the issue, > which is why the new malloc... > > Even once a malloc strace showed no double-frees, not delete of new[] or > malloc'd data etc etc, it would still have that HEAP error. *shrug*. > > Rob > >