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

[Philip Nienhuis]

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

@Lachlan, comment #27:

Oopsie, you're absolutely right about the string comparison.

(below still with your big all-in-one patch, haven't had an opportunity to
build with tip & newer patches)
Right-clicking in the editor margin and entering
strcmp (format, "%f")
in the dialog box emits the same error in the terminal:

>> dbstop in strread at 209 if strcmp (format, "%f")
error: unterminated character string constant
>>


Right clicking in the margin & entering 'format(2) == "f"' (w/o single quotes)
is acceptable (see below) but again yields some error:

>> 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
stopped in
C:\Programs\Octave\Octave-4.1.0+_w64VExTS\share\octave\4.1.0+\m\io\strread.m
at line 209
209:   if (strcmp (typeinfo (format), "sq_string"))
debug> format
format = %f
debug> format(2) == 'f'
ans =  1
debug>



While not very experienced with debugging invoking conditional breakpoints,
I'd expect average users to believe that a "dbstop if ... " should accept any
if condition valid in the context of the function to-be-debugged; even when
introducing new "constants" or "variables" like the 'f' in the example above.
And yes, that would include (user-specified !) any() and all() as an if
condition. But no, dbstop shouldn't substitute those.

As to the CLI, I'm still missing something:
/typing "dbstop ...", not necessarily in the octave-cli executable/
Where else should I enter this dbstop .... command?

Apparently I'm still confused :-)

    _______________________________________________________

Reply to this item at:

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

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