[perl #112312] perl5 version 5.14.2 coredumps during perl -c

On Wed Apr 25 03:38:30 2012, davem wrote:
> I think another suggestion that was mooted a while ago would be to
> allocate OPs from a pool or slab, with a new pool/slab started each time
> we start compiling a new sub, and the pool in some way marked as complete
> at the end of compiling the sub. On croaking, all the OPs in the
> unfinished pools are freed. That way most code doesn't need to be
> modified.

What exactly is that code at the top of op.c that is compiled only when
PL_OP_SLAB_ALLOC is defined?

-- 

Father Chrysostomos


---
via perlbug:  queue: perl5 status: open
https://rt.perl.org:443/rt3/Ticket/Display.html?id=112312

• [perl #112312] perl5 version 5.14.2 coredumps during perl -c by Father Chrysostomos via RT
• Re: [perl #112312] perl5 version 5.14.2 coredumps during perl -c by Dave Mitchell