[Octave-bug-tracker] [bug #41126] dbstop should accept func.m or @class/func.m as argument

[Mike Miller]

Update of bug #41126 (project octave):

                Category:             Interpreter => Octave Function        
        Operating System:                  Mac OS => Any                    
                 Summary: Unable to debug class functions => dbstop should
accept func.m or @class/func.m as argument

    _______________________________________________________

Follow-up Comment #3:

Yes, there are a few missing features of dbstop, see e.g. bug #36874 for
conditional breakpoints. I'm retitling this bug to reflect the compatibility
bug you've stumbled on that the argument should be allowed to be a file with a
.m extension.

It would be good to get some more information about what Matlab does with
different argument types. Are "dbstop func" and "dbstop func.m" always the
same? Do both "dbstop script" and "dbstop script.m" work also, where script.m
is a Matlab script instead of a function file? Does it work with an m-file in
a non-class subdirectory of a directory in the path?

    _______________________________________________________

Reply to this item at:

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

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