bugGNU Octave - Bugs: bug #35795, dbstep doesn't do single line...

 
 

bug #35795: dbstep doesn't do single line stepping when error_status is set

Submitted by:  None
Submitted on:  Sun 11 Mar 2012 11:19:12 PM UTC  
 
Category: NoneSeverity: 3 - Normal
Priority: 5 - NormalItem Group: Incorrect Result
Status: Wont FixAssigned to: None
Originator Name: forkandwaitOriginator Email: -unavailable-
Open/Closed: ClosedRelease: 3.6.1
Operating System: BSD

Add a New Comment(Rich Markup)
   

You are not logged in

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

 

Sat 22 Jun 2013 10:26:09 AM UTC, comment #3:

Since this bug has been marked as "Won't fix" for more than a year can we close it ?

D.

David Bateman <dbateman>
Project Member
Tue 13 Mar 2012 04:39:24 AM UTC, comment #2:

I'm not sure this really is a bug. By the time an error has happened, Octave may have encountered a state it can't recover from... yet you want to recover? I find toggling debug_on_error to be a useful mechanism for figuring out what was the state when the error happened, but not for stepping again. After all, after the error happened, perhaps some variable was expected to be assigned to the value after the error was caught, so what should the debugger do with that variable?

After error status has been set, it seems to me like Octave can drop you into that environment that caused the error, but then it has to rewind and dump you back into the interpreter as soon as possible and get out of the error state as soon as possible.

Jordi GutiƩrrez Hermoso <jordigh>
Project Administrator
Mon 12 Mar 2012 10:16:59 PM UTC, comment #1:

This is a bug and should be fixed.

On the other hand, the preferred method for setting a breakpoint at a specific line is to use the keyboard() function rather than debug_on_error(1)/error("break on this line"). You might use the keyboard() function in the mean time.

Rik <rik5>
Project Administrator
Sun 11 Mar 2012 11:19:12 PM UTC, original submission:

dbstep is behaving in a way I do not expect:

Debugging a function m-file in the current directory, I set debug_on_error(1) and insert a line in the file like "error('sldkjf')". I run the function and get popped into debug mode as I would expect. However, when I dbstep to execute the next line, the function runs to the end and returns (unless there is an error).

Is this to be expected? Is it acting (to my mind) strangely because of the way I am entering debug mode?

Anonymous

 

(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 dbateman (Posted a comment)
  • -unavailable- added by jordigh (Posted a comment)
  • -unavailable- added by rik5 (Posted a comment)
  • -unavailable- added by None (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):

     

     

    Follow 4 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sat 22 Jun 2013 03:15:29 PM UTCrik5Open/ClosedOpen=>Closed
    Fri 16 Mar 2012 03:08:59 AM UTCrik5StatusConfirmed=>Wont Fix
    Mon 12 Mar 2012 10:16:59 PM UTCrik5StatusNone=>Confirmed
      Summarydbstep doesn\'t step single line=>dbstep doesn't do single line stepping when error_status is set

    Back to the top


    Powered by Savane 3.1-cleanup1