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

[Philip Nienhuis]

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

You mean what I saw in comment #2 of bug # 47585?

That still behaves the same. 
Intriguing, and only noting now, is that I didn't see "Hello!" printed to the
screen invoking "run foo", with or without breakpoint.

What I also see is that after "run foo" "dbclear foo" does nothing.
After closing foo.m editor tab and reopening foo.m in the editor, the
breakpoint is cleared and there's no way to put it back.....
as if foo.m disappeared out of some memory slot.

Oh I accidentally hit a clue:

>> which foo
'foo' is a command-line function
>>


... so it morphed into a command line function instead of a .m function on
disk, apparently after the command "run foo".


    _______________________________________________________

Reply to this item at:

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

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