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 with moar with specific PERL6LIB and running a specific test file #3533
Comments
From @usev6I get a segmentation fault with moar when I run the following command (tested on Debian 7 and FreeBSD 10.0): $ PERL6LIB=$(pwd)/lib:. ./perl6-m t/spec/S05-transliteration/trans.rakudo.moar Other values for PERL6LIB ('lib:.' or '/path/to/rakudo/lib:/path/to/rakudo) seem to work: http://pastebin.com/cAzk213S Also setting MVM_SPESH_INLINE_DISABLE=1 avoids the segfault as FROGGS pointed out (link below): For further discussion see http://irclog.perlgeek.de/perl6/2014-09-24#i_9403093 |
From @usev6I tried to narrow the problem down, but was not very successful. With the attached file "trans.t" I can reproduce the segfault: $ PERL6LIB=$(pwd)/lib:. ./perl6-m trans.t If I remove some variable declarations or the last say in that file, the segfault goes away. Even changing the quotation (s/'/"/g or s/"/'/g) avoids the segfault. (On a second system I had to declare some more empty variables to get a segfault. But otherwise it behaves identically.) |
From @usev6use v6; 'ABC'.trans( ('A'=>'a'), ('B'=>'b'), ('C'=>'c') ); 'XYZ'.trans( ('XYZ' => 'xyz') ); 'ABC-DEF'.trans( ('- A..Z' => '_ a..z') ); my ($var1,$var2,$var3,$var4,$var5,$var6,$var7,$var8,$var9,$var10); |
From @usev6This was fixed in MoarVM today (cmp. http://irclog.perlgeek.de/perl6/2014-10-02#i_9446636 and http://irclog.perlgeek.de/perl6/2014-10-02#i_9447562). |
1 similar comment
From @usev6This was fixed in MoarVM today (cmp. http://irclog.perlgeek.de/perl6/2014-10-02#i_9446636 and http://irclog.perlgeek.de/perl6/2014-10-02#i_9447562). |
@usev6 - Status changed from 'new' to 'resolved' |
Migrated from rt.perl.org#122842 (status was 'resolved')
Searchable as RT122842$
The text was updated successfully, but these errors were encountered: