In UNIX platforms your test made Perl enter a 100% CPU loop consisting
of SEGVs on top of SEGVs on top of SEGVS... the below hopefully fixes:
Change 17250 by jhi@alpha on 2002/06/15 15:34:51
Possible cure for
Subject: Re: Thread bug in 5.8RC1 Win32
From: Alessandro Forghieri <[EMAIL PROTECTED]>
Date: Sat, 15 Jun 2002 12:56:35 +0200
Message-ID: <[EMAIL PROTECTED]>
Affected files ...
... //depot/perl/perl.c#441 edit
Differences ...
==== //depot/perl/perl.c#441 (text) ====
Index: perl/perl.c
--- perl/perl.c#440~17194~ Wed Jun 12 04:35:57 2002
+++ perl/perl.c Sat Jun 15 18:34:51 2002
@@ -442,7 +442,8 @@
/* Destroy the main CV and syntax tree */
if (PL_main_root) {
- PL_curpad = AvARRAY(PL_comppad);
+ /* If running under -d may not have PL_comppad. */
+ PL_curpad = PL_comppad ? AvARRAY(PL_comppad) : NULL;
op_free(PL_main_root);
PL_main_root = Nullop;
}
End of Patch.
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
