Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<3BCF42E5.5DD26FB2@rowman.com>
Date:	Thu, 18 Oct 2001 17:00:21 -0400
From:	John Peacock <jpeacock AT rowman DOT com>
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: test failures building perl on cygwin - continued
References:	<3BCC5FD7 DOT 24008 DOT 6FFFE4 AT localhost> <20011016173901 DOT Q21328 AT alpha DOT hut DOT fi> <3BCC5401 DOT 768E5222 AT rowman DOT com> <B0000003722 AT iokaste DOT 192 DOT 168 DOT 5 DOT 5> <3BCD9F5D DOT F67DDDCD AT rowman DOT com> <B0000003723 AT iokaste DOT 192 DOT 168 DOT 5 DOT 5> <3BCDB050 DOT EF9A06C1 AT rowman DOT com> <20011017175510 DOT A5672 AT redhat DOT com> <3BCED667 DOT 833A308C AT rowman DOT com> <20011018142538 DOT B27432 AT redhat DOT com>

Christopher Faylor wrote:
> 
> 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.

No, but if I want to step through the code to see exactly where the
malloc goes awry, I need gdb, don't I.  I'll take a look at this next
week (I am leaving for a long weekend).  Point me at any other docs you
might think useful (like do I need to install a new cygwin root or can
I just copy over the cygwin1.dll?).

Thanks

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747

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

- Raw text -