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
SEGV with rakudo.moar when executing 'next; CONTROL { }' #3774
Comments
From @usev6While trying to silence warnings from tests which use eval_lives_ok, I stumbled upon a segfault with rakudo.moar. The golfed version is: $ perl6-m -e 'next; CONTROL { }' I tried to generate a gdb backtrace: $ cat control.p6 $ gdb --args /home/christian/my_files/computer/Perl6/tmp/rakudo_work_1/install/bin/moar --execname="$0" --libpath="/home/christian/my_files/computer/Perl6/tmp/rakudo_work_1/install/share/nqp/lib" --libpath="." /home/christian/my_files/computer/Perl6/tmp/rakudo_work_1/perl6.moarvm control.p6 Program received signal SIGSEGV, Segmentation fault. |
From @usev6In case it is helpful, here is a gdb backtrace with moar built with --no-optimize (other things being equal): (gdb) bt full |
From @usev6The segfault with MoarVM is fixed. The new error message seems LTA, though. $ perl6-m -e 'next; CONTROL { }' |
1 similar comment
From @usev6The segfault with MoarVM is fixed. The new error message seems LTA, though. $ perl6-m -e 'next; CONTROL { }' |
From @jnthnOn Sun May 03 13:49:54 2015, bartolin@gmx.de wrote:
Indeed. Now it's better: perl6-m -e "next; CONTROL { }" Test in S04-exception-handlers/control.t. |
The RT System itself - Status changed from 'new' to 'open' |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#124255 (status was 'resolved')
Searchable as RT124255$
The text was updated successfully, but these errors were encountered: