[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #56616] dbquit does not accept "all" option
From: |
John W. Eaton |
Subject: |
[Octave-bug-tracker] [bug #56616] dbquit does not accept "all" option |
Date: |
Thu, 11 Jul 2019 17:04:19 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 |
URL:
<https://savannah.gnu.org/bugs/?56616>
Summary: dbquit does not accept "all" option
Project: GNU Octave
Submitted by: jwe
Submitted on: Thu 11 Jul 2019 09:04:17 PM UTC
Category: Interpreter
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Feature Request
Status: None
Assigned to: jwe
Originator Name: jwe
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: Any
_______________________________________________________
Details:
Octave's dbquit function doesn't accept an "all" option.
Additionally, dbquit with no options appears to work like Matlab's "dbquit
all" is documented to behave.
If you execute
dbstop sombrero
sombrero
then execute somebrero again at the "debug> " prompt you should be at the
second level debug prompt (displayed as "[1]debug> "). At that prompt,
executing dbquit with no options should pop you back to the first debug prompt
but Octave will exit the debugger completely and send you all the way back to
the top-level command prompt.
In Matlab, "dbquit" exits one level of the debugger and "dbquit all" exits the
debugger completely.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?56616>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #56616] dbquit does not accept "all" option,
John W. Eaton <=