[Octave-bug-tracker] [bug #46795] dbstop lacks much Matlab functionality

[Philip Nienhuis]

Follow-up Comment #31, bug #46795 (project octave):

Trying the new series of patches (3 pcs), I get:

>> dbstop in strread at 209 if format(2) == "f"
ans =  209
>> strread ("1 2 3", "%f")
warning: Error evaluating breakpoint condition:
    'f' undefined near line 1 column 14
ans =

   1
   2
   3
>> dbclear strread
>> dbstop in strread at 209 if format(2) == '"f"'
ans =  209
>> strread ("1 2 3", "%f")
debug>


so things seem to work well. The double-quoting around %f required in the cli
might be a bit of a nuissance (I fear that people will overlook or forget
this).

With single quotes I get slightly different messages:

>> strread ("1 2 3", "%f")
warning: Error evaluating breakpoint condition:
    'f' undefined near line 1 column 14
stopped in
/home/philip/devel/octdev/oct410+VExTSdbs/../dev_VExTS/scripts/io/strread.m at
line 209
209:   if (strcmp (typeinfo (format), "sq_string"))
debug>


And when entering the condition in the GUI it works w/o double quotes.
In the GUI I also see this: when I right-click and enter a wrong condition
(assignment rather than comparison) I see two error messages: one in the gui,
and
"error: dbstop: condition cannot be an assignment.  Did you mean '=='?"
in the terminal pane.
I think the latter can be dropped if one is working in the editor pane. But of
course this is just a bit nitpicking.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?46795>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/