[perl #40824] [TODO] loadlib opcode causes problems with exceptions
Klaas-Jan Stol via RT
parrotbug-followup at parrotcode.org
Sun Nov 30 13:10:15 UTC 2008
On Sat Nov 11 19:16:33 2006, chromatic at wgz.org wrote:
> On Saturday 11 November 2006 19:01, Bob Rogers wrote:
>
> > I don't think it's loadlib itself; I believe the library :init code
is
> > trying to throw an error. If that is the case, then it's a
continuation
> > barrier problem. Before the error, do you see this "oops" message?
>
> Yes, and agreed. Matt and I discussed that just after he sent the
message.
>
> > I don't recall seeing this "failed assertion" before, though.
> > Probably we should turn this "oops" into an internal_exception,
since
> > memory might be getting corrupted subsequently.
> >
> > The fix was this patch . . .
> >
> > Looks good to me. I see chromatic has already committed this as
> > r15413.
>
> It just gets the test to pass; there are still outstanding questions
with
> regard to exceptions and continuations and the C barrier.
>
> -- c
>
With the developments of the past year, to what extent is/can this still
be an issue? The issue seems to be 2 years old. I seem to remember that
there's a new exception system in place, and that the whole C barrier
thing was worked on at some point.
kjs
More information about the parrot-dev
mailing list