[Octave-bug-tracker] [bug #57902] Confusing debug output from scripts

[Philip Nienhuis]

URL:
  <https://savannah.gnu.org/bugs/?57902>

                 Summary: Confusing debug output from scripts
                 Project: GNU Octave
            Submitted by: philipnienhuis
            Submitted on: Wed 26 Feb 2020 04:16:28 PM CET
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Other
                  Status: None
             Assigned to: None
         Originator Name: Philip Nienhuis
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

When using a "keyboard" statement in scripts the output that follows on screen
is hard to grasp and at times confusing.

I have script calling a function called "cleanup_ints" (both are in the path)
and there's a "keyboard" statement at L. 14 of the script.
When that keyboard statement is hit I get the following output:

>> keyboard> dbstep
stopped in octave_uEiJOH at line 37
[C:\Users\Nienhu01\AppData\Local\Temp\octave\octave_uEiJOH.m]

37: __db_next_breakpoint_quiet__(false);
debug> dbstep
stopped in octave_uEiJOH at line 39
[C:\Users\Nienhu01\AppData\Local\Temp\octave\octave_uEiJOH.m]

39: octave_onhdtq (12, 'endif', 'endif');
debug> dbstep
stopped in octave_uEiJOH at line 42
[C:\Users\Nienhu01\AppData\Local\Temp\octave\octave_uEiJOH.m]

42: octave_onhdtq (13, '  [ints, vals] = cleanup_ints (ints, vals);', ' 
[ints, vals] = cleanup_in
ts (ints, vals);');
debug> dbstep
stopped in octave_uEiJOH at line 43
[C:\Users\Nienhu01\AppData\Local\Temp\octave\octave_uEiJOH.m]

43:   [ints, vals] = cleanup_ints (ints, vals);
debug> dbstep
stopped in cleanup_ints at line 46 [<some network drive>\...\cleanup_ints.m]


The confusion starts when the debug output mentions L.37 while the actual
"keyboard" statement that triggers it is in L.14 of the script.
Also confusing is that Octave echoes the name of the temp scratch script (made
by the interpreter I suppose) which is of little help for users.
Subsequent "dbstep" statements give additional confusing output, until
execution finally lands in the called function "cleanup_ints.m".

The point I want to make here is that a lot of info is echoed to the screen
that is of no immediate use to users, if not confusing because line numbers
don't match what the user sees in the editor.




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57902>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/