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
Error message provokes panic #5615
Comments
From 1parrota@gmail.comAn error in a sprintf format (program attached) generates a "panic" message: Your printf-style directives specify 0 arguments, but 1 argument was supplied Apologies if it should have been reported as a moarvm bug perl6 -v |
From @timoThis sound much more severe than it is. panic is just a convenience method that throws an exception that it then just uses nqp::die to throw that message, which is as harmless |
The RT System itself - Status changed from 'new' to 'open' |
From 1parrota@gmail.com"Panic" brings to mind "kernel panic" - perhaps there's a less Presumably " in any at" should have something between "any" and "at", On 8/26/16, Timo Paulssen via RT <perl6-bugs-followup@perl.org> wrote:
|
From @timowe could call the method "parsefail", or maybe just "fail", or "abort". |
From 1parrota@gmail.comOn 8/26/16, Timo Paulssen via RT <perl6-bugs-followup@perl.org> wrote:
Just plain "fail" seems most appropriate. Even the reference to the VM seems more confusing than useful to the |
From @timoOn 27/08/16 17:45, Parrot Raiser wrote:
Huh? What do you mean "reference to the VM"? |
From 1parrota@gmail.com
in any at /home/guru/rakudo/rakudo-star-2016.07/install/share/perl6/runtime/CORE.setting.moarvm moarvm is mentioned at the end of both lines, (which say nothing |
From @timoare you aware that that's just the filename? and the whole thing is just not necessarily a very useful stacktrace; usually we'd want to have the On 27/08/16 22:11, Parrot Raiser wrote:
|
From @geekosaurOn Sat, Aug 27, 2016 at 4:22 PM, Timo Paulssen <timo@wakelift.de> wrote:
I think you're getting an end user's-eye view of what internal backtraces -- |
From 1parrota@gmail.com
Right! If the problem is simply a user error, (an invalid entry in an I thought I was reporting some problem in the processing or creation On 8/27/16, Brandon Allbery via RT <perl6-bugs-followup@perl.org> wrote:
|
From @jnthnOn Sun Aug 28 10:16:31 2016, 1parrota@gmail.com wrote:
Improved things a good bit in dc7f27988. The sprintf format strings are parsed using a grammar in NQP. When we can't parse it, we call the panic method (a standard name used by the Perl 6 grammar also). This is all fine. What wasn't so fine is that: * We let that leak into the userspace backtrace, where it...well, apparently makes people panic * We accidentally trimmed the userspace backtrace below that line due to some not so smart logic to avoid showing unhelpful stuff. I've fixed those up so that you get a decent backtrace of where the sprintf was now and it doesn't mention the panic method - which is an implementation detail. We should probably write some kind of test for this; I'll tag it testneeded. :-) |
From @zoffixznetTests added in Raku/roast@71aab20a9d |
@zoffixznet - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#129088 (status was 'resolved')
Searchable as RT129088$
The text was updated successfully, but these errors were encountered: