bugGNU Octave - Bugs: bug #42708, Breakpoints should be removed from...

 
 

bug #42708: Breakpoints should be removed from files when changes are saved

Submitted by:  Richard <crobar>
Submitted on:  Tue 08 Jul 2014 02:29:35 PM UTC  
 
Category: GUISeverity: 3 - Normal
Priority: 5 - NormalItem Group: Other
Status: NoneAssigned to: None
Originator Name: Open/Closed: Open
Release: devOperating System: GNU/Linux

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

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

 

Thu 05 Feb 2015 10:34:40 PM UTC, comment #1:

Breakpoint management needs a better arrangement before it can become robust:

https://savannah.gnu.org/patch/?8016

There are a couple aspects of it. One is a more versatile means of communicating between GUI and core. A second is a means to make the breakpoint more object-like with reference to the core's breakpoint and that of the editor (a level of indirection, if you will) so that breakpoints can move appropriately in the editor when the user modifies the file.

Dan Sebald <sebald>
Tue 08 Jul 2014 02:29:35 PM UTC, original submission:

Breakpoints should probably be cleares (or greyed out, or otherwise modified) in the GUI editor when a file with a break points present already is edited and saved to avoid the following behaviour:

Take a function like below:

1. run in terminal, to make sure function is loaded by octave

2. put breakpoint on line 2 (x = 1)

3. edit parse_breakpoint_test () and create a parse error, e.g. modify x = x + 1; to be x = x + ; and save the file

4. run the function again (debugger will stop at line 2, either continue, getting the parse error or quit)

You will now be unable to deselect the break point symbol you created in step 1 which remains showing in the editor. Even after you save the file with the parse error fixed. This persists even if you run the file again, and you can place working break points as normal on the other lines which work.

You cannot now place a break point on this original break point line via the editor. You can still place one using dbstop however, and clicking on the break point in the editor still removes the brek point (although the symbol stays there, and you still can't add it back in again via the editor).

The only way you can 'reset' the editor behaviour I have found so far is to close the file and reopen it.

Richard <crobar>

 

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

Attach File(s):
   
   
Comment:
   

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 sebald (Posted a comment)
  • -unavailable- added by crobar (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):

     

     

    No Changes Have Been Made to This Item

    Back to the top


    Powered by Savane 3.1-cleanup