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
Null PMC access (Parrot) and segfault (JVM) when assigning to a variable "declared" in a subsignature in a variable declaration in Rakudo #3260
Comments
From @masak<BenGoldberg> r: my $a ($b, $c); $b = 42; say $b |
From @usev6Status update: Right now this is no longer a Null PMC access error on Parrot but we get a segfault on Moar as well: $ perl6-m -e 'my $a ($b, $c); $b = 42;' $ perl6-p -e 'my $a ($b, $c); $b = 42;' $ perl6-j -e 'my $a ($b, $c); $b = 42;' |
1 similar comment
From @usev6Status update: Right now this is no longer a Null PMC access error on Parrot but we get a segfault on Moar as well: $ perl6-m -e 'my $a ($b, $c); $b = 42;' $ perl6-p -e 'my $a ($b, $c); $b = 42;' $ perl6-j -e 'my $a ($b, $c); $b = 42;' |
@usev6 - Status changed from 'new' to 'open' |
From @nwc10On Fri, Oct 17, 2014 at 03:08:12AM -0700, Christian Bartolomaeus via RT wrote:
valgrind doesn't spot any undefined behaviour leading up to the SEGV: ==2246== Invalid read of size 8 It's this code (with line numbers): 1223 OP(assign): { I can't convince gdb to "like" the various local libraries on this machine Nicholas Clark |
From @donaldh2015.02 gives this result on both Moar and JVM:
This ticket can probably be closed. |
From @usev6I added a test to S04-declarations/my.t with commit Raku/roast@25f2964446 It only tests that there is no NullPointerException (or no segfault which would abort the test) -- everything else passes. I'm closing this ticket as 'resolved'. |
1 similar comment
From @usev6I added a test to S04-declarations/my.t with commit Raku/roast@25f2964446 It only tests that there is no NullPointerException (or no segfault which would abort the test) -- everything else passes. I'm closing this ticket as 'resolved'. |
@usev6 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#120397 (status was 'resolved')
Searchable as RT120397$
The text was updated successfully, but these errors were encountered: