Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Fri, 13 Jun 2003 02:45:56 +0100
From: Elfyn McBratney <elfyn AT is DOT ubertales DOT co DOT uk>
X-X-Sender: elfyn AT ellixia
Reply-To: cygwin AT cygwin DOT com
To: Michael Checky <Michael_Checky AT Thermoking DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: Patch to allow CVS cygwin enable-malloc-debugging to compile
In-Reply-To: <OF697ECF0C.0B365EFA-ON86256D44.00060140@ingerrand.com>
Message-ID: <Pine.CYG.4.55.0306130243280.1312@ellixia>
References: <OF697ECF0C DOT 0B365EFA-ON86256D44 DOT 00060140 AT ingerrand DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 12 Jun 2003, Michael Checky wrote:

> I needed to enable malloc debugging to track down a memory corruption
> error.  I had to apply this patch to get the CVS version of cygwin to
> compile after running configure with the --enable-malloc-debugging option.
> I didn't do any tests of the dll, but it seemed to work well enough to
> allow me to track down the bug.  In case anybody is interested, I've
> tracked the memory bug it to either arm-elf-gcc 3.3 or arm-elf-ld 2.13.2.1.

You might want to send this to cygwin-patches AT cygwin DOT com , as per
<http://cygwin.com/lists.html>.

Elfyn

-- 
Elfyn McBratney (mailto:spambot AT is DOT ubertales DOT co DOT uk)
Systems Administrator
ABCtales.com / Ubertales.co.uk


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