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: Alessan
> > > _IO_read_end = 0x646e4128 ,
> > > _IO_read_base = 0x73616572 ,
> > > _IO_write_base = 0x202e4a20 ,
> > > _IO_write_ptr = 0x6eb6c34b ,
> > > _IO_write_end = 0x20296769 ,
> > > _IO_buf_base = 0x69736976 ,
> > > _IO_buf_end = 0x20646574 ,
> > > _IO_save_base = 0x20656874
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
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
On Tue, Jun 11, 2002 at 08:23:18AM -0700, Doug MacEachern wrote:
> On Tue, 11 Jun 2002, Andreas J. Koenig wrote:
>
> > PAUSE is suffering from a SEGV since I installed RC1. After I upgraded
> > yesterday to snapshot 17165 I finally caught the following within gdb.
There was something funky with
Hi,
sorry for not answering sooner. The suggested patch seems to work
find with the development branch of Perl, and I believe Sarathy
will apply the patch also to the maintenance branch.
On Wed, Feb 21, 2001 at 09:32:04PM +0100, Jens-Uwe Mager wrote:
> On Fri, Feb 16, 2001 at 05:44:34PM +0100,
