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: <3BC1AA89.555837A2@rowman.com>
Date: Mon, 08 Oct 2001 09:30:49 -0400
From: John Peacock <jpeacock AT rowman DOT com>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Perl 5.7.2
References: <NCBBIHCHBLCMLBLOBONKKEPBCGAA DOT g DOT r DOT vansickle AT worldnet DOT att DOT net> <3BC181BC DOT 28728 DOT 27AFF272 AT localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Gerrit P. Haase" wrote:
> 
> I don't think that it is a good idea to bundle an 'unstable' development
> version.  Perl 5.8 will be released soon and then it will be 'stable'.
> We should wait until 5.8.
> 

It is especially inappropriate to include Perl 5.7.2 (or 5.8.0) until 
it will build/test without core dumps when Perl is built for debugging.
See

	http://www.cygwin.com/ml/cygwin/2001-10/msg00067.html

for more details.  By downgrading to CygWin 1.3.2-2, I was able to
get around the problems with gdb refusing to break at statements, but
I am still getting cores for roughly a third of the overall tests
during the perl_destruct phase.  I am unable to replicate it while
running under gdb, so I am at a loss where to go next.  I will post
another message with more details.

John Peacock

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