Skip to content
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

Unhandled exception: This representation (VMException) does not support attribute storage #1263

zoffixznet opened this issue Nov 21, 2017 · 1 comment


None yet
3 participants
Copy link

commented Nov 21, 2017

Came across this while doing some DIHWIDT, figured I'd file it in case this crash is hiding the real error:

$ perl6 -v
This is Rakudo version 2017.11-2-g575d31e built on MoarVM version 2017.11
implementing Perl 6.c.

$ cat Foo.pm6 
BEGIN True does False;

$ perl6 -I. -MFoo -e ''
Unhandled exception: This representation (VMException) does not support attribute storage (for type BOOTException)
   at SETTING::src/core/  (/home/zoffix/rakudo/install/share/perl6/runtime/CORE.setting.moarvm:print_exception)
 from SETTING::src/core/  (/home/zoffix/rakudo/install/share/perl6/runtime/CORE.setting.moarvm:<anon>)
 from gen/moar/stage2/NQPHLL.nqp:1708  (/home/zoffix/rakudo/install/share/nqp/lib/NQPHLL.moarvm:command_eval)
 from src/Perl6/Compiler.nqp:42  (/home/zoffix/rakudo/install/share/nqp/lib/Perl6/Compiler.moarvm:command_eval)
 from gen/moar/stage2/NQPHLL.nqp:1630  (/home/zoffix/rakudo/install/share/nqp/lib/NQPHLL.moarvm:command_line)
 from gen/moar/main.nqp:47  (/home/zoffix/rakudo/install/share/perl6/runtime/perl6.moarvm:MAIN)
 from gen/moar/main.nqp:38  (/home/zoffix/rakudo/install/share/perl6/runtime/perl6.moarvm:<mainline>)
 from <unknown>:1  (/home/zoffix/rakudo/install/share/perl6/runtime/perl6.moarvm:<main>)
 from <unknown>:1  (/home/zoffix/rakudo/install/share/perl6/runtime/perl6.moarvm:<entry>)

This comment has been minimized.

Copy link

commented May 24, 2018

This is as far as I have traced this:

nqp::getmessage on the original exception itself gives "Malformed UTF-8". The exception proceeds down to the call to $e.backtrace in print_exception. Once it enters method backtrace, it throws the exception about the original exception not supporting attributes... which of course should not happen as the method is a class method on an Exception. From there, the new exception aborts the try and enters the $! clause. Attempting to put any note statements in method backtrace causes a busy loop in stage optimize when building rakudo.

Something is jumping the rails.

@lucasbuchala lucasbuchala added the MoarVM label Mar 15, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.