[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #38982] Debugger re-executes previous command
From: |
Dan Sebald |
Subject: |
[Octave-bug-tracker] [bug #38982] Debugger re-executes previous command when typing only carriage-return |
Date: |
Tue, 14 May 2013 03:43:29 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15 |
URL:
<http://savannah.gnu.org/bugs/?38982>
Summary: Debugger re-executes previous command when typing
only carriage-return
Project: GNU Octave
Submitted by: sebald
Submitted on: Tue 14 May 2013 03:43:27 AM GMT
Category: Interpreter
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Incorrect Result
Status: None
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: GNU/Linux
_______________________________________________________
Details:
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.,
if (! __octave_link_enabled__ ())
then type "uigetfile" at the command line in the terminal window.
When the debugger breaks, type "disp(varargin)" at the command line. I see:
debug> disp(varargin)
{}(0x0)
Now, type just a carriage return (no up arrow) a couple times. I see:
debug> disp(varargin)
{}(0x0)
debug>
{}(0x0)
debug>
{}(0x0)
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?38982>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #38982] Debugger re-executes previous command when typing only carriage-return,
Dan Sebald <=