Menu

#429 Regina 3.8 error message displays as: Error %d running "%.s": %.s

v3.9.1
closed-fixed
None
5
2016-01-20
2014-06-15
No

Syntax errors are sometimes displayed as

Error %d running "%.s": %.s

This has been observed with error 64 prior to execution and error 41 during interactive tracing.

Related

Bugs: #430

Discussion

  • Mark Hessling

    Mark Hessling - 2014-06-22
    • assigned_to: Mark Hessling
     
  • Mark Hessling

    Mark Hessling - 2014-06-22

    An incorrect mechanism for handling error strings introduced in v3.8 causes invalid error messages to be displayed or the occasional crash.

     
  • Mark Hessling

    Mark Hessling - 2014-06-23
    • status: open --> pending
    • Group: v3.8RC1 --> v3.8.2
     
  • Mark Hessling

    Mark Hessling - 2014-06-23

    Fixed in v3.8.2

     
  • Paul Kislanko

    Paul Kislanko - 2014-07-03

    In REXX-Regina_3.8.2(MT) 5.00 22 Jun 2014
    the "occaisional crash" is now quite frequent.

     
  • Mark Hessling

    Mark Hessling - 2014-07-04

    I have tested this version with various combinations of error types with and without interactive tracing and even interpret and can't get Regina to crash. Can you give me a specific small test case that always crashes on your system please.
    Also what platform are you getting these errors on?

     
  • Paul Kislanko

    Paul Kislanko - 2014-07-11

    Environment and circumstances

    parse version v;say v
    REXX-Regina_3.8.2(MT) 5.00 22 Jun 2014
    parse source s;say s
    WIN64 COMMAND D:\Documents\Football\2014\Zrexxshell.rx
    do i=1 to 4;say sourceline(i);end
    / REXX "shell" /
    trace '?i'
    nop / enter REXX clause(s), typically CALL or var=function() /
    exit
    call 'globaldata'()
    ----------------^^^
    results in
    3 +++ nop / enter REXX clause(s), typically CALL or var=function() /
    and then the
    Regina Rexx Launcher (x64) has stopped working

    A problem caused the program to stop working correctly.
    Windows will close the program and notify you if a solution is
    available.


    I consistently produce this by forgetting mid-clause whether I'm invoking an external routine (or RexxUtil function) via the CALL or function interface.

    So it is 1) interactive tracing; 2) a syntax error in the input stream, specifically incorrect CALL syntax. It is clear Regina is trying to report the error, since the +++ line is displayed.

    Cheers!

     

    Last edit: Paul Kislanko 2014-07-11
  • Mark Hessling

    Mark Hessling - 2014-07-15

    Thanks Paul. Yes can replicate this with your test case. Will fix and send you a version to test.

     
    • Paul Kislanko

      Paul Kislanko - 2014-07-25

      Tested, and Regina no longer crashes in any of the cases where it did before. Thanks!

       
  • Mark Hessling

    Mark Hessling - 2015-04-04
    • Group: v3.8.2 --> v3.9.1
     
  • Mark Hessling

    Mark Hessling - 2016-01-20
    • status: pending --> closed-fixed
     

Log in to post a comment.