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

[Michael C. Grant]

Follow-up Comment #6, bug #41126 (project octave):

Mike, good questions.

Here's what I can see: if I have a function '@cvx/norm.m', all three of these
commands successfully set a breakpoint to the first line:


dbstop @cvx/norm
dbstop @cvx/norm.m
dbstop @cvx/norm.p


Yes, that last one works, even if the '.p' file does not exist. These produce
an error:


dbstop @cvx/norm.mex
dbstop @cvx/norm.mexmaci
dbstop @cvx/norm.mexmaci64


This extension behavior is identical for normal functions, scripts, and class
functions.

The subdirectory approach does *not* work for non-class subdirectories in the
path. To test this, I created a subdirectory 'test' and a script in my
~/Documents/MATLAB directory, which is in my path. The "edit" command below
succeeds, but the "dbstop" command fails. If I try use the editor to set a
breakpoint in test/command_test.m, I get the modal dialog.


>> cd ~/Documents/MATLAB
>> edit test/command_test.m
>> dbstop test/command_test.m
Error using dbstop
Cannot find function "test/command_test.m".


    _______________________________________________________

Reply to this item at:

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

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