Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: "Dan Osborne" To: Subject: RE: Memory debugging under cygwin Date: Mon, 11 Oct 2004 11:44:02 +0100 Message-ID: <002501c4af7f$38d0c550$eb88510a@internal.specialist.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit In-Reply-To: <4166BFFE.2000104@x-ray.at> X-Ramesys-Professional-Services-MailScanner-Information: Please contact the ISP for more information X-Ramesys-Professional-Services-MailScanner: Found to be clean X-Ramesys-Professional-Services-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (score=-3.4, required 5, IN_REP_TO -3.38) Note-from-DJ: This may be spam Reini Urban wrote: >>> Great shame that valgrind isn't ported to cygwin! > > but dmalloc is. > after libtoolizing and autoreconf with latest autotools just add > AM_WITH_DMALLOC to your configure.in Hmmm, I've yet to bite the libtool bullet but if it gets dmalloc working maybe nows the time to do it. For C++ do you still have to override new and delete yourself or has AM_WITH_DMALLOC done it automatically? Also, where would people recommend I start investigating libtool - http://sources.redhat.com/autobook/autobook/autobook_toc.html? Thanks, Dan -- 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/