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 statements." It's good advice, particularly for debugging something in a loop. Michael On Wed, Feb 8, 2012 at 5:25 PM, ikuzar <[email protected]> wrote: > 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.789695.n4.nabble.com/basic-debugging-tp4371113p4371113.html > Sent from the R help mailing list archive at Nabble.com. > > ______________________________________________ > [email protected] mailing list > https://stat.ethz.ch/mailman/listinfo/r-help > PLEASE do read the posting guide http://www.R-project.org/posting-guide.html > and provide commented, minimal, self-contained, reproducible code. ______________________________________________ [email protected] mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
