| Line 26... |
Line 26... |
| 26 |
\details{
|
26 |
\details{
|
| 27 |
Each call to \code{browser} can supply either a text string or a condition.
|
27 |
Each call to \code{browser} can supply either a text string or a condition.
|
| 28 |
The functions \code{browserText} and \code{browserCondition} provide ways
|
28 |
The functions \code{browserText} and \code{browserCondition} provide ways
|
| 29 |
to retrieve those values. Since there can be multiple browser contexts
|
29 |
to retrieve those values. Since there can be multiple browser contexts
|
| 30 |
active at any time we also support retrieving values from the different
|
30 |
active at any time we also support retrieving values from the different
|
| 31 |
contexts. The innermost (most recently initiated) browser context is
|
31 |
contexts. The innermost (most recently initiated) browser context is
|
| 32 |
numbered 1: other contexts are numbered sequentially.
|
32 |
numbered 1: other contexts are numbered sequentially.
|
| 33 |
|
33 |
|
| 34 |
\code{browserSetDebug} provides a mechanism for initiating the browser in
|
34 |
\code{browserSetDebug} provides a mechanism for initiating the browser in
|
| 35 |
one of the calling functions. See \code{\link{sys.frame}} for a more
|
35 |
one of the calling functions. See \code{\link{sys.frame}} for a more
|
| 36 |
complete discussion of the calling stack. To use \code{browserSetDebug}
|
36 |
complete discussion of the calling stack. To use \code{browserSetDebug}
|
| 37 |
you select some calling function, determine how far back it is in the call
|
37 |
you select some calling function, determine how far back it is in the call
|
| 38 |
stack and call \code{browserSetDebug} with \code{n} set to that value.
|
38 |
stack and call \code{browserSetDebug} with \code{n} set to that value.
|
| 39 |
Then, by typing \code{c} at the browser prompt you will cause evaluation
|
39 |
Then, by typing \code{c} at the browser prompt you will cause evaluation
|
| 40 |
to continue, and provided there are no intervening calls to browser or
|
40 |
to continue, and provided there are no intervening calls to browser or
|
| 41 |
other interrupts, control will halt again once evaluation has returned to
|
41 |
other interrupts, control will halt again once evaluation has returned to
|
| 42 |
the closure specified. This is similar to the up functionality in gdb
|
42 |
the closure specified. This is similar to the up functionality in gdb
|
| 43 |
or the "step out" functionality in other debuggers.
|
43 |
or the "step out" functionality in other debuggers.
|
The R Project SVN
R