On Thu, Dec 02, 2004 at 08:09:41PM -0800, Brian Ingerson wrote:
> On 02/12/04 21:03 -0600, Steve Peters wrote:
> > On Thu, Dec 02, 2004 at 06:04:11PM -0800, Brian Ingerson wrote:
> > > ...
> > > Is there a fast fix to this, or should I start looking for a workaround?
[...]
> > Anyways, foo() seems to be the sticking point. Changing @_ to @foo and
> > passing it to bar rather than doing a goto seems to work. I've tried
There seen to be a few changes in the Perl 5.8.6 changes that seem to
be suspicious. If the goto &bar isn't working the following two changes
seem to be working on that functionality.
Change 23217 by [EMAIL PROTECTED] on 2004/08/14 22:32:16
make pp_goto() cope potential stack reallocation in EXTEND
The code for goto &foo had local pointers to the stack that
pointed to the wrong place after a realloc.
Change 23418 by [EMAIL PROTECTED] on 2004/10/23 21:50:19
[perl #32039] Chained goto &sub drops data too early.
Change 22373 to stop a memory leak in goto &foo intead caused
the elements of @_ to be freed too early. This revised fix
just transfers the reifiedness of the old @_ to the new @_
> >
> > As for the actual cause, it is likely related to how @DB::args is
> > getting populated, but since I don't know how that is happening, I
> > can't be much more help for you.
>
> Steve, Thanks for looking into this. Hopefully I can clarify the
> situation a bit. First a small intro to what broke:
[...]
Thanks for the explanation on the DB trick. I'll have to take a close
look into that. Its getting late for me, but hopefully the changes I
noted above should give something for others to look into.
Steve Peters
[EMAIL PROTECTED]
