[perl #119801] Modifying @DB::dbline entries can crash perl

On Wed Oct 30 21:29:27 2013, sprout wrote:
> On Mon Oct 28 22:02:51 2013, sprout wrote:
> > On Mon Sep 16 23:53:11 2013, sprout wrote:
> > > How about having an array shared between threads and indexed by
> > > cop_seq?
> > >
> > > Or, if that makes the array too long, extend the struct for dbstate
> > > ops
> > > and store a separate sequence number.
> > >
> > > When the op is freed, it can invalidate its entry.  We would need
> > > three
> > > values: 0 = no op available, 1 = no breakpoint, 2 = breakpoint set.
> > >
> > > The numeric values stored in @DB::dbline elements would be indices
> > > into
> > > that breakpoint array.
> >
> > Please review the attached patch, which is also on the sprout/dbline
> > branch.
> 
> In particular, does B::C need to access the extra fields that dbstate
> ops now have, or can we keep the cop–dbop distinction private?

Having received no response, I applied this yesterday, as c1cec775e.

-- 

Father Chrysostomos

• [perl #119801] Modifying @DB::dbline entries can crash perl by Father Chrysostomos via RT
• Re: [perl #119801] Modifying @DB::dbline entries can crash perl by Jim Cromie