Re: debug breakpoint commands want line numbers as strings!!

[David Bateman]

David Bateman wrote:
> John W. Eaton wrote:
>> On 22-May-2007, David Bateman wrote:
>>
>> | The commandline form would still work.. However we are a long way from
>> | Matlab compatible here. A typical breakpoint might be
>> | 
>> | dbstop in foo at 10 if a == 10
>> | 
>> | and debug_on_error etc in Matlab are in fact
>> | 
>> | debug if error
>> | 
>> | It seems like a lot of work to get full compatibility here. so maybe later.
>>
>> I think we need to find someone who has a passion for writing debuggers.
>>
>> OK, is there anything else that should go in before 2.9.11?
>>
>> jwe
>>
> 
> Maybe, this.. I forgot to document dbstep, dbnext and dbcont..
> 

With slightly better english.. Its late here

D.

Index: doc/interpreter/debug.txi
===================================================================
RCS file: /usr/local/cvsroot/octave/doc/interpreter/debug.txi,v
retrieving revision 1.3
diff -u -r1.3 debug.txi
--- doc/interpreter/debug.txi   22 May 2007 02:27:43 -0000      1.3
+++ doc/interpreter/debug.txi   22 May 2007 03:02:06 -0000
@@ -26,7 +26,7 @@
 @noindent
 in debug mode. However, writing the above in three lines will not be
 correctly evaluated. To leave the debug mode, you should simply type
-either @code{quit} or @code{exit}.
+either @code{quit}, @code{exit}, @code{return} or @code{dbcont}.
 
 @menu
 * Entering Debug Mode::
@@ -116,3 +116,13 @@
 @DOCSTRING(dbwhere)
 
 @DOCSTRING(dbtype)
+
+Debug mode equally allows single line stepping through a function. To
+allow this two additional commands are available; @code{dbstep} and
address@hidden These differ slightly in the way they treat the next
+executable line if the next line itself is a function defined in an
+m-file.
+
address@hidden will execute the next line, while staying in the existing
+function being debugged. Whereas @code{dbstep} will step in to this new
+function defined in an m-file.