[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #41126] dbstop should accept func.m or @class/func.m as argument
Date: Tue, 07 Jan 2014 02:54:40 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36

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:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]