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: <3BCED667.833A308C@rowman.com>
Date: Thu, 18 Oct 2001 09:17:27 -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>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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.

If you can get the gdb bug fixed, even as a slipstream patch that I 
will have to apply myself, I can work vs 1.3.3.  Otherwise, the only 
thing I can do go back to a known configuration and try and work 
forward in time.

> 
> We seem to have inexplicably skipped back to the "I dunno I think it's
> 1.3.3" stage of the discussion, for some reason.  This could easily be
> the case but the fact that perl is dying in a call to free() does not
> pinpoint the issue enough to draw that conclusion.
> 

I'm not running 1.3.3, I am running 1.3.2.  I do not lightly accuse
CygWin of being at fault.  But I have tried Perl distributions known to
have tested clean before, and they now core during the cleanup phase.  
So if the application behavior has changed, but the application has 
not, that is very strong evidence that the underlying code (being 
CygWin) has to be the primary suspect.  It might not be cygwin1.dll 
itself; it may be gcc that is messing up an optimization, or it may be 
some other library that was updated in the last 3 months.

I may have to go back in time and install only those modules of CygWin
available in early July and then, assuming I can get clean builds, 
slowly work forward until everything goes south.

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/