Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Thu, 18 Oct 2001 22:00:03 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: test failures building perl on cygwin - continued Message-ID: <20011018220003.B11830@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20011016173901.Q21328@alpha.hut.fi> <3BCC5401.768E5222@rowman.com> <3BCD9F5D.F67DDDCD@rowman.com> <3BCDB050.EF9A06C1@rowman.com> <20011017175510.A5672@redhat.com> <3BCED667.833A308C@rowman.com> <20011018142538.B27432@redhat.com> <3BCF42E5.5DD26FB2@rowman.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BCF42E5.5DD26FB2@rowman.com> User-Agent: Mutt/1.3.21i On Thu, Oct 18, 2001 at 05:00:21PM -0400, John Peacock wrote: >No, but if I want to step through the code to see exactly where the >malloc goes awry, I need gdb, don't I. Early in this discussion, Egor Duda suggested that you take a look at a document that he wrote called "how-to-debug-cygwin.txt". This tells you how to configure cygwin with malloc debugging. This causes cygwin to go through very extensive tests on each malloc/free and report on block overruns or double frees with information about where the block was first allocated. This is what I mean by malloc debugging. cgf -- 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/