Thanks again, Hendrik, for your help. Your suggestion would work. You
could even wrap the save image and the dump.frames command in one
function that is called when an error occours.
I now, however, wrapped a dummy function around the call to source
that starts my script and supplies a copy o
I somehow was unsure whether or not your procedure was interactive or not. But when it is
non-interactive, your problem remains: "If recover is called in non-interactive mode, it
behaves like dump.frames" (and will likely not save the global environment."
The only othjer idea I have is that you
Thanks, Henrik for your reply. Well, the reason (until now) was that I
thought recover would only work in interactive sessions. The question,
however, no would be how to save the error object an daccess it later.
Additionally, are you sure that the content of the global environment is
saved wit
Dear Jannis,
is there any specific reason you use dump.frames instead of recover? As far as
I see it, options(error = recover) would allow to access the global environment.
And as ?recover tells you: "The use of recover largely supersedes dump.frames as an
error option, unless you really want
Dear list members,
I am trying to use dump.frames to debug some code that i run non
interactively. I use the following method:
dump.frames.mod = function() {
dump.frames(dumpto = 'test', to.file = TRUE)
quit(save = 'no', status = 10)
}
options(error = dump.frames.mod)
Is there any w
5 matches
Mail list logo
