Re: [R] basic debugging

2012-02-08 Thread Bert Gunter
?options ## error = recover will allow you to browse state at the point of error ?traceback ## invoke immediately after an error to see exactly in which function the error occurred -- Bert On Wed, Feb 8, 2012 at 9:01 PM, ilai wrote: > ?debug will satisfy your curiosity regarding "debug mode"  

Re: [R] basic debugging

2012-02-08 Thread ilai
?debug will satisfy your curiosity regarding "debug mode" - strictly speaking it is not a "mode", just another function. On Wed, Feb 8, 2012 at 7:30 PM, R. Michael Weylandt wrote: > What is your question? More interestingly, what is "debug mode" in R? > > I'd suggest you look at traceback() --

Re: [R] basic debugging

2012-02-08 Thread R. Michael Weylandt
What is your question? More interestingly, what is "debug mode" in R? I'd suggest you look at traceback() -- there's also the powerful, but possibly advanced, options(error=recover) Kerninghan said "The most effective debugging tool is still careful thought, coupled with judiciously placed print

[R] basic debugging

2012-02-08 Thread ikuzar
Hi, I have to debug my program. When I execute my function (in debug mode), I have got an error but I do not know which line is concerned. I do not want to do an infinite "Browse[2]>n with each line in my function... THanks for your help, ikuzar -- View this message in context: http://r.7896