Displaying 7 results from an estimated 7 matches for "showerrorcalls".
2009 Nov 24
1
ow to have R automatically print traceback upon errors
...onder how to have R automatically print stack trace produced by
traceback upon errors during interactive uses. I tried the suggestions on
http://old.nabble.com/Automatically-execute-traceback-when-execution-of-script-causes-error--td22368483.html#a22368775
and used options(error = recover)
options(showErrorCalls = T)
It just produces an extra message like "recover called non-interactively;
frames dumped, use debugger() to view"
Thanks
Jeff
2008 Jan 16
1
Automatic traceback
I would like to have an automatic traceback printed on error. Is there
a way to do this?
options(error=traceback) seems to print the previous error, not the
current error. I'm guessing this is because the traceback is not set
until the error handler is done running.
> options(error=traceback)
> stop("1")
Error: 1
No traceback available
> stop("2")
Error: 2
1:
2009 Mar 06
1
Automatically execute traceback when execution of script causes error?
Hi
I am using R scripts which are running remotely. To make debugging
easier, I would like to have the possibility to execute traceback()
automatically when an error occurs. Is this possible?
OS: Linux
Thanks
Rainer
--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Faculty of Science
Natural
2012 Jun 22
0
R 2.15.1 is released
...A as documented.
o Closing an X11() window while locator() was active could abort
the R process.
o getMethod(f, sig) produced an incorrect error message in some
cases when f was not a string).
o Using a string as a "call" in an error condition with
options(showErrorCalls=TRUE) could cause a segfault. (PR#14931)
o The string "infinity" allowed by C99 was not accepted as a
numerical string value by e.g. scan() and as.character().
(PR#14933)
o In legend(), setting some entries of lwd to NA was inconsistent
(depending on the graph...
2012 Jun 22
0
R 2.15.1 is released
...A as documented.
o Closing an X11() window while locator() was active could abort
the R process.
o getMethod(f, sig) produced an incorrect error message in some
cases when f was not a string).
o Using a string as a "call" in an error condition with
options(showErrorCalls=TRUE) could cause a segfault. (PR#14931)
o The string "infinity" allowed by C99 was not accepted as a
numerical string value by e.g. scan() and as.character().
(PR#14933)
o In legend(), setting some entries of lwd to NA was inconsistent
(depending on the graph...
2007 Oct 03
1
R-2.6.0 is released
...ted, now the one with highest version number.
o optim(method = "L-BFGS-B") now accepts zero-length parameters,
like the other methods. Also, method = "SANN" no longer
attempts to optimize in this case.
o New options 'showWarnCalls' and 'showErrorCalls' to give a
concise traceback on warnings and errors. showErrorCalls=TRUE
is the default for non-interactive sessions. Option
'showNCalls' controls how abbreviated the call sequence is.
o New options 'warnPartialMatchDollar', 'warnPartialMatch...
2007 Oct 03
1
R-2.6.0 is released
...ted, now the one with highest version number.
o optim(method = "L-BFGS-B") now accepts zero-length parameters,
like the other methods. Also, method = "SANN" no longer
attempts to optimize in this case.
o New options 'showWarnCalls' and 'showErrorCalls' to give a
concise traceback on warnings and errors. showErrorCalls=TRUE
is the default for non-interactive sessions. Option
'showNCalls' controls how abbreviated the call sequence is.
o New options 'warnPartialMatchDollar', 'warnPartialMatch...