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:
On Thu, Jun 13, 2002 at 06:52:13PM +0200, Andreas J. Koenig wrote:
On Wed, 12 Jun 2002 23:45:41 +0200, [EMAIL PROTECTED] (Andreas J.
Koenig) said:
Currently I have a testcase that is still 7300 lines of perl code for
the server (after all these are in one file) but only 50 lines for
On Thu, Jun 13, 2002 at 08:26:30PM +0200, Andreas J. Koenig wrote:
On Thu, 13 Jun 2002 10:32:01 -0700 (PDT), Doug MacEachern [EMAIL PROTECTED]
said:
On Thu, 13 Jun 2002, Andreas J. Koenig wrote:
Program received signal SIGSEGV, Segmentation fault.
0x400ed761 in _IO_fflush
_IO_read_end = 0x646e4128 Address 0x646e4128 out of bounds,
_IO_read_base = 0x73616572 Address 0x73616572 out of bounds,
_IO_write_base = 0x202e4a20 Address 0x202e4a20 out of bounds,
_IO_write_ptr = 0x6eb6c34b Address 0x6eb6c34b out of bounds,
_IO_write_end =
