December 12, 2016

(This article was first published on R – Greetz to Geeks, and kindly contributed to R-bloggers)

We often come across errors while coding. In R, when a function returns an error, there is an easy way to figure out which command have triggered the error. All we need is to use the traceback function.

This helps a developer to find out where and why the error occured. Once the error is traced it is easy for debugging and rectifying the error. The function syntax is as follows,


The traceback() by default prints the call stack of the last error. Apart from tracing the errors, this function is also helpful in times if we require to print the current stack.

Note: The errors caught via try or tryCatch will not generate a traceback

To leave a comment for the author, please follow the link and comment on their blog: R – Greetz to Geeks. offers daily e-mail updates about R news and tutorials on topics such as: Data science, Big Data, R jobs, visualization (ggplot2, Boxplots, maps, animation), programming (RStudio, Sweave, LaTeX, SQL, Eclipse, git, hadoop, Web Scraping) statistics (regression, PCA, time series, trading) and more...

If you got this far, why not subscribe for updates from the site? Choose your flavor: e-mail, twitter, RSS, or facebook...

Comments are closed.

Search R-bloggers


Never miss an update!
Subscribe to R-bloggers to receive
e-mails with the latest R posts.
(You will not see this message again.)

Click here to close (This popup will not appear again)