The R Project SVN R

Rev

Rev 30896 | Rev 39406 | Go to most recent revision | Show entire file | Ignore whitespace | Details | Blame | Last modification | View Log | RSS feed

Rev 30896 Rev 35081
Line 28... Line 28...
28 
  Typing \code{where} causes the debugger to print out the current
 28 
  Typing \code{where} causes the debugger to print out the current
29 
  stack trace (all functions that are active).
 29 
  stack trace (all functions that are active).
30 
  If you have variables with names that are identical to the controls
 30 
  If you have variables with names that are identical to the controls
31 
  (eg. \code{c} or \code{n} ) then you need to use \code{print(c)} and
 31 
  (eg. \code{c} or \code{n} ) then you need to use \code{print(c)} and
32 
  \code{print(n)} to evaluate them.
 32 
  \code{print(n)} to evaluate them.
- 
 
 33 
 
- 
 
 34 
  In order to debug S4 methods (see \code{\link[methods]{Methods}}), you
- 
 
 35 
  need to use \code{\link{trace}}, typically calling \code{\link{browser}},
- 
 
 36 
  e.g., as \cr
- 
 
 37 
  \code{trace("plot", browser, exit=browser, signature = c("track", "missing"))}
33 
}
 38 
}
34 
\seealso{
 39 
\seealso{
35 
  \code{\link{browser}}, \code{\link{traceback}} to see the stack after
 40 
  \code{\link{browser}}, \code{\link{trace}};
36 
  an \code{Error: \dots} message; \code{\link{recover}} for another
 41 
  \code{\link{traceback}} to see the stack after an \code{Error: \dots}
37 
  debugging approach.
 42 
  message; \code{\link{recover}} for another debugging approach.
38 
}
 43 
}
39 
\keyword{programming}
 44 
\keyword{programming}
40 
\keyword{environment}
 45 
\keyword{environment}