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
Pre-compiled MoarVM-code segfaults on type-checking #4261
Comments
From andrspv@gmail.comDummy.pm: use File::Temp; use Dummy; % perl6 --target=mbc --output=blib/Dummy.pm.moarvm lib/Dummy.pm Backtrace: (gdb) bt full (gdb) print MVM_dump_backtrace(tc) |
From @stmukusing perl6-valgrind-m ==28463== |
The RT System itself - Status changed from 'new' to 'open' |
From @jnthnWorking on this, but it golfs further to this module: subset File of Str; And then just pre-compiling it and doing: use Dummy; |
From @jnthnOn Mon Jun 29 07:52:32 2015, jnthn@jnthn.net wrote:
And now fixed, and this golfed version added as a test in S10-packages/precompilation.t. |
@jnthn - Status changed from 'open' to 'resolved' |
For the record (and re-using this ticket since it is linked from roast): On the JVM backend the test in S10-packages/precompilation started to fail after timo/rakudo@1acc4d3258.
I've fudged the test with Raku/roast@44685318d2 (for the JVM backend). |
Migrated from rt.perl.org#125245 (status was 'resolved')
Searchable as RT125245$
The text was updated successfully, but these errors were encountered: