Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: "Gerrit P. Haase" Organization: Esse keine toten Tiere To: cygwin AT cygwin DOT com Date: Fri, 19 Oct 2001 00:25:40 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: test failures building perl on cygwin - continued Reply-to: cygwin AT cygwin DOT com Message-ID: <3BCF7304.1414.5E26762C@localhost> In-reply-to: <20011018142538.B27432@redhat.com> References: <3BCED667 DOT 833A308C AT rowman DOT com> X-mailer: Pegasus Mail for Win32 (v3.12cDE) X-Hops: 1 X-Sender: 320081107336-0001 AT t-dialin DOT net Christopher Faylor schrieb am 2001-10-18, 14:25: > On Thu, Oct 18, 2001 at 09:17:27AM -0400, John Peacock wrote: >> Christopher Faylor wrote: >>> On Wed, Oct 17, 2001 at 12:22:40PM -0400, John Peacock wrote: >>>>So it appears that both bleadperl and 5.6.1 have something that is not >>>>clean under CygWin. The next task is to build cygwin1.dll with the >>>>additional memory debugging and try and track it down. >>> >>>IIRC, this was the "next step" that was suggested the last time this >>>issue was raised. >> >>I have taken this step with 1.3.3, but I am still hampered by the now >>identified gdb bug, which is what is really holding me back now. Now >>that I know that 1.3.3 is not going to play nice with gdb under a Win2K >>workstation in an NT domain (is that qualified enough for you ;~), I >>need to go back and get a copy of the last 1.3.2 source and build the >>augmented dll there. > >What does building cygwin with malloc debugging have to do with gdb? >You don't need gdb to use this. How do I do that? What is the difference to a 'normal' debug version? Thanks, Gerrit -- =^..^= -- 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/