[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #51522] break points not caught when debugging

From: Marshall
Subject: [Octave-bug-tracker] [bug #51522] break points not caught when debugging file in private folder
Date: Thu, 20 Jul 2017 21:10:14 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:54.0) Gecko/20100101 Firefox/54.0


                 Summary: break points not caught when debugging file in
private folder
                 Project: GNU Octave
            Submitted by: marsian
            Submitted on: Fri 21 Jul 2017 01:10:12 AM UTC
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: Marsian
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.2.1
        Operating System: Microsoft Windows



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.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]