[Octave-bug-tracker] [bug #51522] break points not caught when debugging file in private folder

[Marshall]

Follow-up Comment #2, bug #51522 (project octave):

Somewhat related: trying to add a breakpoint in a class function (e.g. in an
@... folder), the same prompt comes up. Adding the folder to the path does
allow stopping at the break point, but then the class may have defined
functions which will shadow others. That can become a mess.

Work around: after adding the folder to the path, and setting the breakpoint,
the folder can be removed from the path and the breakpoint still works.

Doing the same for files in private folders doesn't work and the breakpoints
are (eventually) cleared if the private folder is removed from the path.

Octave can obviously find these files (class or private functions), why can't
break points be set and caught in them?

    _______________________________________________________

Reply to this item at:

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

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