Mercurial > octave-nkf
comparison doc/interpreter/debug.txi @ 8828:8463d1a2e544
Doc fixes.
* 2]$$. => 2].$$
* @var{extrapval} => @var{extrapval}.
* call helloworld.oct => called @file{helloworld.oct}
* @itemize => @table @code
* shows. => shows:
* save => @code{save}
* @ref{Breakpoints} => @pxref{Breakpoints}
* add @noindent following example
* which is computed => and compute it
* clarify wording
* remove comma
* good => well
* set => number
* by writing => with the command
* has the option of directly calling => can call
* [-like-] {+of the right size,+}
* solvers => routines
* handle => test for
* add introductory section
* add following
* {+the+} [0..bitmax] => [0,bitmax]
* of the => with
* number => value
* add usual
* Besides when doing comparisons, logical => Logical {+also+}
* array comparison => array, comparisons
* param => parameter
* works very similar => is similar
* strings, => strings
* most simple => simplest
* easier => more easily
* like => as
* called => called,
* clarify wording
* you should simply type => use
* clarify wording
* means => way
* equally => also
* [-way much-] {+way+}
* add with mean value parameter given by the first argument, @var{l}
* add Functions described as @dfn{mapping functions} apply the given
operation to each element when given a matrix argument.
* in this brief introduction => here
* It is worth noticing => Note
* add following
* means => ways
author | Brian Gough <bjg@network-theory.co.uk> |
---|---|
date | Fri, 20 Feb 2009 11:17:01 -0500 |
parents | 03b7f618ab3d |
children | eb63fbe60fab |
comparison
equal
deleted
inserted
replaced
8827:55d999c23728 | 8828:8463d1a2e544 |
---|---|
39 | 39 |
40 @node Entering Debug Mode | 40 @node Entering Debug Mode |
41 @section Entering Debug Mode | 41 @section Entering Debug Mode |
42 | 42 |
43 There are two basic means of interrupting the execution of an Octave | 43 There are two basic means of interrupting the execution of an Octave |
44 script. These are breakpoints @ref{Breakpoints}, discussed in the next | 44 script. These are breakpoints @pxref{Breakpoints}, discussed in the next |
45 section and interruption based on some condition. | 45 section and interruption based on some condition. |
46 | 46 |
47 Octave supports three means to stop execution based on the values set in | 47 Octave supports three means to stop execution based on the values set in |
48 the functions @code{debug_on_interrupt}, @code{debug_on_warning} and | 48 the functions @code{debug_on_interrupt}, @code{debug_on_warning} and |
49 @code{debug_on_error}. | 49 @code{debug_on_error}. |
55 @DOCSTRING(debug_on_error) | 55 @DOCSTRING(debug_on_error) |
56 | 56 |
57 @node Leaving Debug Mode | 57 @node Leaving Debug Mode |
58 @section Leavinging Debug Mode | 58 @section Leavinging Debug Mode |
59 | 59 |
60 To leave the debug mode, you should simply type either @code{dbcont} | 60 To leave the debug mode, use either @code{dbcont} |
61 or @code{return}. | 61 or @code{return}. |
62 | 62 |
63 @DOCSTRING(dbcont) | 63 @DOCSTRING(dbcont) |
64 | 64 |
65 To quit debug mode and return directly to the prompt @code{dbquit} | 65 To quit debug mode and return directly to the prompt @code{dbquit} |
105 27. The breakpoints can then be cleared with the @code{dbclear} function | 105 27. The breakpoints can then be cleared with the @code{dbclear} function |
106 | 106 |
107 @DOCSTRING(dbclear) | 107 @DOCSTRING(dbclear) |
108 | 108 |
109 @noindent | 109 @noindent |
110 To clear all of the breakpoints in a function the recommended means, | 110 These functions can be used to clear all the breakpoints in a function. For example, |
111 following the above example, is then | |
112 | 111 |
113 @example | 112 @example |
114 dbclear ("asind", dbstatus ("asind")); | 113 dbclear ("asind", dbstatus ("asind")); |
115 @end example | 114 @end example |
116 | 115 |
138 @end example | 137 @end example |
139 | 138 |
140 Note that @code{filemarker} returns a character that marks the | 139 Note that @code{filemarker} returns a character that marks the |
141 subfunctions from the file containing them. | 140 subfunctions from the file containing them. |
142 | 141 |
143 Another simple means of setting a breakpoint in an Octave script is the | 142 Another simple way of setting a breakpoint in an Octave script is the |
144 use of the @code{keyboard} function. | 143 use of the @code{keyboard} function. |
145 | 144 |
146 @DOCSTRING(keyboard) | 145 @DOCSTRING(keyboard) |
147 | 146 |
148 @noindent | 147 @noindent |
165 You may also use @code{isdebugmode} to determine whether the debugger is | 164 You may also use @code{isdebugmode} to determine whether the debugger is |
166 currently active. | 165 currently active. |
167 | 166 |
168 @DOCSTRING(isdebugmode) | 167 @DOCSTRING(isdebugmode) |
169 | 168 |
170 Debug mode equally allows single line stepping through a function using | 169 Debug mode also allows single line stepping through a function using |
171 the commands @code{dbstep}. | 170 the commands @code{dbstep}. |
172 | 171 |
173 @DOCSTRING(dbstep) | 172 @DOCSTRING(dbstep) |
174 | 173 |
175 @node Call Stack | 174 @node Call Stack |