Re: [perl #23965] Data::Dumper + threads + recursion = segfault

On Thu, Jul 14, 2005 at 01:58:08AM -0700, Michael G Schwern via RT wrote:
> > [davem - Tue Sep 23 17:09:43 2003]:
> > 
> > On Mon, Sep 22, 2003 at 05:01:19PM -0000, David Buckley wrote:
> > > use threads;
> > > use threads::shared;
> > > use Data::Dumper;
> > > our $a : shared;
> > > $a = \$a;
> > > print Data::Dumper::Dumper( $a );
> > > 
> > > This produces a short pause, then a segfault.
> > 
> > The segfault is due to stack or memory exhaustion caused by infinite
> > recursion. The problem is due to the 'proxy' per-thread variables
> > failing to detect a loop caused by mg_get().
> 
> This is still an issue in bleadperl@25129.

Fixed in bleed by change #26695

-- 
A walk of a thousand miles begins with a single step...
then continues for another 1,999,999 or so.

• [perl #23965] Data::Dumper + threads + recursion = segfault by Michael G Schwern via RT
• Re: [perl #23965] Data::Dumper + threads + recursion = segfault by Dave Mitchell