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 Message-ID: <4166BFFE.2000104@x-ray.at> Date: Fri, 08 Oct 2004 18:27:42 +0200 From: Reini Urban 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 CC: Dan Osborne , cygwin AT cygwin DOT com Subject: Re: Memory debugging under cygwin References: <41663A31 DOT 7070902 AT emirates DOT net DOT ae> In-Reply-To: <41663A31.7070902@emirates.net.ae> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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/