[Octave-bug-tracker] [bug #33411] Breakpoints aren't hit with run command

[Philip Nienhuis]

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

Lachlan, after applying your patch to 4.1.0+:

>> dbstop isdir 26
ans =  26
>> isdir
stopped in
/home/philip/devel/octdev/oct410+VExTS/../dev_VExTS/scripts/general/isdir.m at
line 26
26:   if (nargin != 1)
debug> dbcont
stopped in
/home/philip/devel/octdev/oct410+VExTS/../dev_VExTS/scripts/general/isdir.m at
line 26
26:   if (nargin != 1)
debug> dbcont
error: Invalid call to isdir.  Correct usage is:

 -- isdir (F)

Additional help for built-in functions and operators is
available in the online version of the manual.  Use the command
'doc <topic>' to search the manual index.

Help and information about Octave is also available on the WWW
at http://www.octave.org and via the address@hidden
mailing list.
>> run isdir
>> run isdir
>>


I may not understand fully, but isn't the breakpoint supposed to be hit when
doing "run isdir", similarly to just "isdir" ?


    _______________________________________________________

Reply to this item at:

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

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