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
From: "Ralf Habacker" <Ralf DOT Habacker AT freenet DOT de>
To: "Brian Genisio" <briang AT OasisAdvancedEngineering DOT com>, <cygwin AT cygwin DOT com>
Subject: RE: Debug malloc?
Date: Sat, 9 Nov 2002 02:53:54 +0100
Message-ID: <001001c28792$dc2ac280$be6007d5@BRAMSCHE>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
In-reply-to: <IFFC1TSE0VPWVFD83BA1TICNKMHLH98.3dcc0885@briang>
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal

> Hi all,
>
> Is there a debug version of malloc for cygwin that I can link
> against?  I am trying to track down a sneaky memory leak.
>
http://sourceforge.net/project/showfiles.php?group_id=27249&release_id=121299

Try this malloc debugging library and let me know if this helps.

I have used this to find some memory related issues with the cygwn port of kde.
You only have to link this library to your application.

After your application has finished it prints a list of unfreed memory areas and
their calling address, which is printable as source line if your application is
compiled with debugging informations.

Additional you can log all memory related calls.

Regards

Ralf



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/