Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: Fri, 13 Dec 2002 08:53:59 -0500
From: Jason Tishler <jason AT tishler DOT net>
Subject: Does configure with --enable-malloc-debugging build?
To: Cygwin-Developers <cygwin-developers AT cygwin DOT com>
Mail-followup-to: Cygwin-Developers <cygwin-developers AT cygwin DOT com>
Message-id: <20021213135359.GC1704@tishler.net>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
User-Agent: Mutt/1.4i

I'm trying to debug a potential heap corruption problem in Cygwin Python
so I configured with --enable-malloc-debugging.  Unfortunately, I get
the following build errors (after make clean):

    g++ -c -gstabs+ -O2 -MMD -fbuiltin ... malloc_wrapper.cc
    ../../../../src/winsup/cygwin/malloc_wrapper.cc:50: type specifier omitted
       for parameter
    ../../../../src/winsup/cygwin/malloc_wrapper.cc:50: parse error before
       string constant
    ../../../../src/winsup/cygwin/malloc_wrapper.cc: In function `void* 
       malloc_dbg(...)':
    ...

Is the above caused by the switch from newlib's malloc to a recent
version of Doug Lea's malloc?  Or, is this cockpit error?

Thanks,
Jason

-- 
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6