bugGNU Octave - Bugs: bug #38982, Debugger re-executes previous...

 
 

bug #38982: Debugger re-executes previous command when typing only carriage-return

Submitted by:  Dan Sebald <sebald>
Submitted on:  Tue 14 May 2013 03:43:27 AM UTC  
 
Category: InterpreterSeverity: 3 - Normal
Priority: 5 - NormalItem Group: Incorrect Result
Status: InvalidAssigned to: None
Originator Name: Open/Closed: Closed
Release: devOperating System: GNU/Linux

Add a New Comment(Rich Markup)
   

You are not logged in

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

 

Tue 14 May 2013 04:12:43 AM UTC, comment #2:

OK, I can see that, at least in the case of "dbstep". For other commands, I'm not sure repeating the previous is helpful for much. Can you think of any? Instead, it might be nicer to just map CR in debug mode to "dbstep". For example, one could then do

instead of having to type

Also, if there is the repeat command feature, what are your thoughts about leaving debug-mode commands out of the command history? It seems to me to be convenient to not have those commands in the history because when I'm done debugging chances are good I want to run the command again that triggers the breakpoint and do some more debugging after I've made changes I think will fix the problem.

I've argued in the past that any command that changes workspace memory should be in the command history, and I think that is a good argument. But in the case of the debug repeat feature, we can't have a completely accurate representation of the history. One can't tell if the user typed:

or

as an example.

Dan Sebald <sebald>
Tue 14 May 2013 03:49:09 AM UTC, comment #1:

That behavior is intentional, and it is patterned after similar behavior in GDB. It makes it easier to step through a function, because you don't have to keep typing or recalling the dbstep command (for example).

John W. Eaton <jwe>
Project Administrator
Tue 14 May 2013 03:43:27 AM UTC, original submission:

Inside the debugger, hitting carriage-return will re-run the previous command. As an example, open uigetfile.m in the editor window and set a breakpoint at the first line inside the function, i.e.,

then type "uigetfile" at the command line in the terminal window.

When the debugger breaks, type "disp(varargin)" at the command line. I see:

Now, type just a carriage return (no up arrow) a couple times. I see:

Dan Sebald <sebald>

 

(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 jwe (Posted a comment)
  • -unavailable- added by sebald (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 2 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Tue 14 May 2013 03:49:09 AM UTCjweStatusNone=>Invalid
      Open/ClosedOpen=>Closed

    Back to the top


    Powered by Savane 3.1-cleanup1