[Octave-bug-tracker] [bug #60733] more on : how to identify the statement which prints output to the console ?

[PIERRE LABRECHE]

Follow-up Comment #4, bug #60733 (project octave):


I work on a large Octave program ( several thousand lines of code ), and it
may generate console oputput such as " retval = ... ... ... ... ... " spitting
large arrays at high speed.  Even when more on is used, it is very tedious to
locate the culprit statement that is not terminated by a semicolon.

If only I could display the state of the debug stack.
Unfortunately, it is not a feature of the current version of Octave.

Note: I regularly insert keyboard() calls, because GUI breakpoints do not work
with classdef OO-style code. Thanks anyway for the tip !

[comment #3 commentaire #3 :]
> if you wish to stop at a certain line of your script/function you can use
the keyboard function or set a breakpoint. Stopping depending on the number of
outputs and (in case of more on) the size of the console widget is not
suitable for debugging.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message posté via Savannah
  https://savannah.gnu.org/