Re: Perl 5.7.2

[John Peacock <jpeacock at rowman dot com>]

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/