New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown method on Exception causes segfault #2457
Comments
From brian.gernhardt@mail.rit.eduWhile testing out CATCH, I tried the Rosetta Code example for exceptions: http://rosettacode.org/wiki/Exceptions#Perl_6
This quite unhelpfully segfaulted. I finally golfed it down to:
Some experimenting discovered that any unknown method on an Exception causes a segfault:
|
From @pmichaudThis is very likely a duplicate of RT #64262. The problem is that exceptions thrown from inside of a CATCH block (in Rakudo uses Parrot ExceptionHandlers to implement CATCH blocks. We need Note that simply using "pop_eh" to remove the ExceptionHandler from the Pm |
The RT System itself - Status changed from 'new' to 'open' |
From @jnthnOn Sun Jul 31 22:22:25 2011, brian.gernhardt@mail.rit.edu wrote:
Many things have improved with exceptions in Rakudo of late, and it
Tagging testneeded. /jnthn |
From @moritzExceptions are in no way special anymore, and we have tests for the |
@moritz - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#96028 (status was 'resolved')
Searchable as RT96028$
The text was updated successfully, but these errors were encountered: