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: <3BC30401.2D09A965@rowman.com>
Date: Tue, 09 Oct 2001 10:04:49 -0400
From: John Peacock <jpeacock AT rowman DOT com>
MIME-Version: 1.0
To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
CC: cygwin AT cygwin DOT com
Subject: Re: Perl 5.7.2
References: <3BC1CF2E DOT 7177 DOT 33050F17 AT localhost> <3BC1B8C0 DOT C1E58D08 AT rowman DOT com> <20011008115635 DOT A18826 AT redhat DOT com> <3BC1D323 DOT 861B6670 AT rowman DOT com> <20011008150120 DOT A19660 AT redhat DOT com> <3BC1FF9D DOT 6BA1CEB AT rowman DOT com> <005501c15090$30366b30$0200a8c0 AT lifelesswks>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Robert Collins wrote:
> 
> Or in short, to make useful progress debugging the development branch of
> a unix-originated piece of software you really need:
> 1) a unix box. (emulated a la vmware will do)
> 2) a win32 machine with cygwin CVS built with debugging.
> 3) the software you want to debug, on both 1) and 2), first eliminate
> all common bugs, then the remainder are cygwin related. Filter the
> conditions I listed above on the remaining bugs and you will have two
> lists:
> a) fix-in-your code bugs
> b) _potential_ cygwin bugs
> 

[good discussion truncated]

All valid points; currently the development branch of Perl is building
100% clean on virtually all well supported O/S's (pick your *nix 
distro) and almost clean on things as variable as OS/X (Not Really 
Unix[tm]) and VMS.  

The problem I am seeing under Cygwin is an aberration, both for Perl 
and Cygwin.  I had clean debug builds as late as last month.  It only 
has problems under Perl-Built-For-Debugging (and three minor test 
failures I have not gotten around to digging into).  Almost all tests 
succeed (even with PBFD); the cores only happen when exiting the 
program (during cleanup apparently).

This smells like a CygWin problem, only under Win2k and only on certain
machines.  If we can catch it happening, we can stomp it.  The problem
is that anything newer than 1.3.2-2 breaks debugging under Win2K for
me (and at least Roman Belenov).  That is a different problem which I
think has to be fixed before we can get close to finding out what Perl
is up to.

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/