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
NativeCall MoarVM panic #6364
Comments
From Vladimir.Marek@oracle.comI took the NativeCall sample from here: https://perl6advent.wordpress.com/2015/12/21/day-21-nativecall-backs-and-beyond-c/ use NativeCall; sub XML_SetElementHandler(OpaquePointer $parser, sub XML_ParserCreate(Str --> OpaquePointer) is native('expat') { ... } my $xml = q:to/XML/; my $depth = 0; sub start-element($, $elem, $attr) sub end-element($, $elem) my $parser = XML_ParserCreate('UTF-8'); my $buf = $xml.encode('UTF-8'); XML_ParserFree($parser); All works fine, unless I try to use the $attr in start-element sub start-element($, $elem, $attr) The program then terminates with: MoarVM panic: Internal error: Unwound entire stack and missed handler I have seen that on Solaris, but Linux has the same issue. In both cases Thank you |
From @dwarringCan confirm this is still current behaviour with Rakudo 2019. I have came across exactly the same issue and found this ticket. I've noticed, If I change the example to catch exceptions. It then runs: sub start-element($, $elem, $attr) Produces: open calendar Underlying issue seems to be that any uncaught exception in a NativeCall Perl callback currently results in a unfriendly NativeCall MoarVM panic. The exception itself is lost. On Tue, 27 Jun 2017 05:59:08 -0700, Vladimir.Marek@oracle.com wrote:
|
The RT System itself - Status changed from 'new' to 'open' |
Migrated from rt.perl.org#131666 (status was 'open')
Searchable as RT131666$
The text was updated successfully, but these errors were encountered: