Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID:	<4166BFFE.2000104@x-ray.at>
Date:	Fri, 08 Oct 2004 18:27:42 +0200
From:	Reini Urban <rurban AT x-ray DOT at>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8a3) Gecko/20040817
MIME-Version:	1.0
To:	Maarten Boekhold <boekhold AT emirates DOT net DOT ae>
CC:	Dan Osborne <dan DOT osborne AT ramesys DOT com>, cygwin AT cygwin DOT com
Subject:	Re: Memory debugging under cygwin
References:	<MLECJOCAOOEMHIHMOACLMEOGCCAA DOT dan DOT osborne AT ramesys DOT com> <41663A31 DOT 7070902 AT emirates DOT net DOT ae>
In-Reply-To:	<41663A31.7070902@emirates.net.ae>
X-IsSubscribed:	yes

Maarten Boekhold schrieb:
> Dan Osborne wrote:
>> Could you get the test program to work? That shows how it wants to play.
>>
>> The only problem I found with it was that it wouldn't follow shared 
>> objects.
> 
> 
> Yeah, that seems to be the problem I have to. Unfortunately the memory 
> corruption I'm looking for is *in* a shared object. And compiling the 
> whole app static isn't an option, because it also involves a dynamically 
> loaded module :(
> 
>> 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

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