-
Notifications
You must be signed in to change notification settings - Fork 1
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
NullPointerException when calling a sub which runs EVAL on minimal role declaration #3559
Comments
From @usev6I got a NullPointerException with a golfed version of a failing test from roast (test for RT #114380 in S14-roles/basic.t). The test in question uses "eval_lives_ok" which does something similiar to the golfed example via Test.pm. The test in question runs fine with "lives_ok" instead of "eval_lives_ok" $ perl6-j --version $ perl6-j -e "sub foo { EVAL 'role R { }' }; foo; say 'alive'" Using EVAL on the role declaration directly doesn't fail: $ perl6-j -e "EVAL 'role R { }'; say 'alive'" With the help from psch (http://irclog.perlgeek.de/perl6/2014-10-17#i_9527240) I tried to get some more info with jdb, but everything I got was: ==== VM Started: No frames on the current call stack main[1] catch java.lang.NullPointerException Exception occurred: java.lang.NullPointerException (to be caught at: 64411D3B4B0DBD5895A2F295CC3F75570C8D73C2.qb_54(), line=1,497 bci=2,686)"thread=main", org.perl6.nqp.runtime.Ops.getobjsc(), line=3,811 bci=1 main[1] up The application exitedAdditional informations where available with --ll-exception: ====
|
From @donaldhFixed by Raku/nqp@0c4096e1e7 |
The RT System itself - Status changed from 'new' to 'open' |
From @usev6I added a test to S14-roles/basic.t with commit Raku/roast@62ca417fa2 I'm closing this ticket as 'resolved'. |
1 similar comment
From @usev6I added a test to S14-roles/basic.t with commit Raku/roast@62ca417fa2 I'm closing this ticket as 'resolved'. |
@usev6 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#123002 (status was 'resolved')
Searchable as RT123002$
The text was updated successfully, but these errors were encountered: