X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Message-ID:	<47DC48C0.20602@x-ray.at>
Date:	Sat, 15 Mar 2008 23:08:00 +0100
From:	Reini Urban <rurban AT x-ray DOT at>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.8.1.12) Gecko/20080201 SeaMonkey/1.1.8
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Memory leak checking for Cygwin applications
References:	<loom DOT 20080314T215226-313 AT post DOT gmane DOT org>
In-Reply-To:	<loom.20080314T215226-313@post.gmane.org>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

Michael Chen schrieb:
> What do the Cygwin development team recommend for checking memory
> leaks/violations in Cygwin applications (C/C++)?
> 
> Valgrind is not available for Cygwin, and I am told by IBM/Rational that
> PurifyPlus for Windows does not (and I confirmed) support GCC compiled code.

I only remember dmalloc as generic enough library.

Most bigger packages coded there own internal macros
to check for leaks.
-- 
Reini Urban
http://phpwiki.org/  http://murbreak.at/

--
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/

- Raw text -