bugGNU Octave - Bugs: bug #51522, break points not caught when...


bug #51522: break points not caught when debugging file in private folder

Submitted by:  Marshall <marsian>
Submitted on:  Fri 21 Jul 2017 01:10:12 AM UTC  
Category: NoneSeverity: 3 - Normal
Priority: 5 - NormalItem Group: None
Status: ConfirmedAssigned to: None
Originator Name: MarsianOpen/Closed: Open
Release: 4.2.1Operating System: Microsoft Windows

Add a New Comment(Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


Tue 25 Jul 2017 09:34:15 PM UTC, comment #2:

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?

Marshall <marsian>
Fri 21 Jul 2017 06:51:44 AM UTC, comment #1:

This still (also) happens in the dev version (4.3.0+) => confirmed.
I've seen this behavior for a long time but IIRC there is a bug report about it.
Ah found it - bug #41515 - it is not exactly the same but strongly related.

It does work for "keyboard" statements inserted in functions in private folders so there's at least some workaround (but a somewhat rough alternative, admittedly).

Philip Nienhuis <philipnienhuis>
Project Member
Fri 21 Jul 2017 01:10:12 AM UTC, original submission:

If I try to debug a file in a private folder, by setting a breakpoint in the gui by clicking in the margin, I get a dialogue box "Change Directory or Add Directory to Load Path", with options to "Change Directory", "Add Directory to Load Path", or "Cancel". Changing the directory isn't an option, and Cancel won't mark the break point in the GUI. Adding to path allows the breakpoint to be set and can be verified to have been set by using the dbstatus command. However, the debugger won't stop at those breakpoints. The file can be stepped into and stepped through (whether or not the private folder is added to the path), but dbcont will not stop at the breakpoint.

Marshall <marsian>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -unavailable- added by marsian (Submitted the item)

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.


    Please enter the title of George Orwell's famous dystopian book (it's a date):



    Follows 1 latest change.

    Date Changed By Updated Field Previous Value => Replaced By
    Fri 21 Jul 2017 06:51:44 AM UTCphilipnienhuisStatusNone=>Confirmed

    Back to the top

    Powered by Savane 3.1-cleanup1