Thank you everybody for your help.
I am sure using the information you provided I'll be able to do better than
my current approach of using "cat" to trace my programmes!
cheers
Worik
[[alternative HTML version deleted]]
__
R-help@r-project.org
Worik R wrote:
Related: I found the problem eventually. It was a parameter that was too
large and the function called "stop".
Looking at the documentation I see I can supply my own error handler. Cool.
Are there already written error handlers that dump a stack trace?
See http://www.stat
Worik R wrote:
Related: I found the problem eventually. It was a parameter that was too
large and the function called "stop".
Looking at the documentation I see I can supply my own error handler. Cool.
Are there already written error handlers that dump a stack trace?
Is ?traceback what you
Related: I found the problem eventually. It was a parameter that was too
large and the function called "stop".
Looking at the documentation I see I can supply my own error handler. Cool.
Are there already written error handlers that dump a stack trace?
cheers
Worik
On Thu, Mar 18, 2010 at 2:
I have a large programme that after running half an hour or so fails with an
error
Error in x[value] <- NA : only 0's may be mixed with negative subscripts
How can I find out where that error occurs?
If I have to do a binary search using error messages it will take a long
time! Is there some wa
5 matches
Mail list logo
