bugGNU Octave - Bugs: bug #46928, [debug mode] [GUI] fails to reset...

 
 

bug #46928: [debug mode] [GUI] fails to reset breakpoint after error occurs

Submitted by:  None
Submitted on:  Mon 18 Jan 2016 09:53:36 AM UTC  
 
Category: GUISeverity: 3 - Normal
Priority: 5 - NormalItem Group: Incorrect Result
Status: In ProgressAssigned to: None
Originator Name: nicmusOriginator Email: -unavailable-
Open/Closed: OpenRelease: 4.0.0
Operating System: GNU/Linux

Add a New Comment(Rich Markup)
   

You are not logged in

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

 

Sat 02 Jul 2016 01:53:04 AM UTC, comment #3:

The attached patch causes several problems. Retagging as "In progress" from "Patch submitted".

Lachlan Andrew <lachlan>
Project Member
Wed 24 Feb 2016 06:29:13 AM UTC, comment #2:

Here is a draft patch change to allow "clear all" not to remove breakpoints.

When the GUI is active, the focus seems to alternate between the edit window and the command window for a short period after clearing a function. I'm not sure the best way to fix that. Perhaps there should be a general mechanism for opening an edit window without giving it focus, and that should be used by the debug related functions.

(file #36448)

Lachlan Andrew <lachlan>
Project Member
Tue 19 Jan 2016 12:04:06 AM UTC, comment #1:

The behaviour has changed since 4.0.0, especially with changeset 0a09c3cae800, but this script is still problematic.

Now, the "clear all" clears the breakpoints but does not update the GUI's markers for them, and they cannot be removed by clicking on the marker. (For some reason, it sill stops at a breakpoint after the clear all, even though dbstatus shows that breakpoint not being present.)

Once bug #46795 has been fixed to allow dbstop(s) for a structure s, I plan to write a patch to restore all breakpoints after clear all or clear -f. Does that sound a reasonable approach? The alternative is to cause the symbols to be removed after clear all or clear -f

Lachlan Andrew <lachlan>
Project Member
Mon 18 Jan 2016 09:53:36 AM UTC, original submission:

Try this code:

Set a break point wherever and run the script in debug mode.
Everything works fine.

Now comment the line "b = 2;" and run again the code with some breakpoint enabled.

The script fails with an error and the debug mode is halted.
Now it is no longer possible to unset/reset the previous breakpoint. It is necessary to close and open again the script.

Anonymous

 

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

Attach File(s):
   
   
Comment:
   

Attached Files
file #36448:  bug_46928_clear_keeps_breakpoints.cset added by lachlan (2KiB - application/octet-stream)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by mtmiller (Updated the item)
  • -unavailable- added by lachlan (Posted a comment)
  •  

    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):

     

     

    Follow 7 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sat 02 Jul 2016 01:53:04 AM UTClachlanStatusPatch Submitted=>In Progress
    Tue 28 Jun 2016 01:14:38 AM UTClachlanCategoryInterpreter=>GUI
      Item GroupSegfault, Bus Error, etc.=>Incorrect Result
    Wed 24 Feb 2016 06:29:13 AM UTClachlanStatusPostponed=>Patch Submitted
    Wed 24 Feb 2016 06:29:12 AM UTClachlanAttached File-=>Added bug_46928_clear_keeps_breakpoints.cset, #36448
    Sun 21 Feb 2016 10:20:01 PM UTCmtmillerCategoryNone=>Interpreter
      StatusNone=>Postponed

    Back to the top


    Powered by Savane 3.1-cleanup1