Displaying 3 results from an estimated 3 matches for "foundavailable".
2016 Nov 15
2
Missing objects using dump.frames for post-mortem debugging of crashed batch jobs. Bug or gap in documentation?
...-devel and observe a semantic
difference when playing with the parameters:
# Test script 1
g <- "global"
f <- function(p) {
l <- "local"
dump.frames()
}
f("parameter")
results in
# > debugger()
# Message: object 'server' not foundAvailable environments had calls:
# 1: source("~/.active-rstudio-document", echo = TRUE)
# 2: withVisible(eval(ei, envir))
# 3: eval(ei, envir)
# 4: eval(expr, envir, enclos)
# 5: .active-rstudio-document#9: f("parameter")
#
# Enter an environment number, or 0 to exit
#...
2016 Nov 15
0
Missing objects using dump.frames for post-mortem debugging of crashed batch jobs. Bug or gap in documentation?
...he parameters:
>
> # Test script 1
> g <- "global"
> f <- function(p) {
> l <- "local"
> dump.frames()
> }
> f("parameter")
>
> results in
> # > debugger()
> # Message: object 'server' not foundAvailable environments had calls:
> # 1: source("~/.active-rstudio-document", echo = TRUE)
> # 2: withVisible(eval(ei, envir))
> # 3: eval(ei, envir)
> # 4: eval(expr, envir, enclos)
> # 5: .active-rstudio-document#9: f("parameter")
> #
> # Enter an env...
2016 Nov 13
2
Missing objects using dump.frames for post-mortem debugging of crashed batch jobs. Bug or gap in documentation?
Dear R friends,
to allow post-mortem debugging In my Rscript based batch jobs I use
tryCatch( <R expression>,
error = function(e)
{
dump.frames(to.file = TRUE)
})
to write the called frames into a dump file.
This is similar to the method recommended in the "Writing R extensions"
manual in section 4.2 Debugging R code (page 96):