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
Segfault when creating a Sub object and trying to say it #4312
Comments
From @jonathanstoweJust experimenting: perl6 -e 'my $f = Sub.new(); say $f' gdb output: Program received signal SIGSEGV, Segmentation fault. valgrind output: |
From @usev6After Rakudo commit a6d2edc644 this command dies (with X::AdHoc): $ perl6 -e 'my $f = Sub.new(); say $f' I added a test to S06-other/misc.t with commit Raku/roast@ff2dc709fd I'm closing this ticket as 'resolved'. |
1 similar comment
From @usev6After Rakudo commit a6d2edc644 this command dies (with X::AdHoc): $ perl6 -e 'my $f = Sub.new(); say $f' I added a test to S06-other/misc.t with commit Raku/roast@ff2dc709fd I'm closing this ticket as 'resolved'. |
|
@usev6 - Status changed from 'new' to 'resolved' |
From @jonathanstoweHi, my $a = Sub(0); Program received signal SIGSEGV, Segmentation fault. On Mon Jun 15 13:37:59 2015, bartolin@gmx.de wrote:
|
|
@jonathanstowe - Status changed from 'resolved' to 'open' |
From @jnthnOn Sat Jun 20 15:06:05 2015, jns+bc@gellyfish.co.uk wrote:
Hunted down the various SEGVs in MoarVM and fixed those. Also added another test for the original bug that the nice error message did not cover (so exposing the VM SEGV), along with a test for the Sub(0) case. |
|
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#125376 (status was 'resolved')
Searchable as RT125376$
The text was updated successfully, but these errors were encountered: