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
Passing an Exception object to Failure.new segfaults (SEGV) in sink context in Rakudo #3799
Comments
From @masak<lucasb> m: Failure.new(Exception.new) |
From @jnthnOn Fri May 01 06:16:20 2015, masak wrote:
It no longer SEGVs: C:\consulting\rakudo>perl6-m -e "Failure.new(Exception.new); 1" But that probably isn't the right behavior either. So, the MoarVM bug that caused the SEGV is gone, but we should figure out the Rakudo behavior we want. |
The RT System itself - Status changed from 'new' to 'open' |
From @AlexDanielHeh, this behavior lives its own life. See https://gist.github.com/Whateverable/df882a7545b2aa4cd0575909934f4c48 Since 2017.07 it is producing this message: Died with Exception Actually thrown at: I think that's reasonable. Marking as 「testneeded」. On 2015-05-01 07:34:20, jnthn@jnthn.net wrote:
|
@zoffixznet - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#124434 (status was 'resolved')
Searchable as RT124434$
The text was updated successfully, but these errors were encountered: