Re: [rt.cpan.org #88341] Pad corruption under threaded 5.18

Zefram wrote:
> Father Chrysostomos via RT wrote:
> >The following snippet shows a bad interaction between
> >Devel::CallParser and the padrange optimisation:
> ...
> >Perl commit 7601007 fixes this.
> 
> I think it's introduced a related bug.  With Perl 5.19.4 and D:CP 0.001
> I see this crash:
>
> $ cat t1
> use Devel::CallParser;                 
> my($a, $b, $c, $d);
> my($e, $f, $g, $h);
> 1;
> $ perl5.19.4 t1
> zsh: segmentation fault  perl5.19.4 t1

That code fails an assertion for me before it even reaches the path
that 7601007 modified.

It’s more likely that using NULL for uninitialised array entries is
what is making it crash.  It probably fails an assertion on a debug-
ging 5.18.[01].

aa033da fixes it.

• Re: [rt.cpan.org #88341] Pad corruption under threaded 5.18 by Zefram
• Re: [rt.cpan.org #88341] Pad corruption under threaded 5.18 by Father Chrysostomos