[ESS] debugging, mostly tracebug

Vitalie Spinu spinuvit at gmail.com
Sat Apr 6 11:20:13 CEST 2013

  >> Ross Boylan <ross at biostat.ucsf.edu>
  >> on Fri, 05 Apr 2013 16:57:54 -0700 wrote:

 > On 4/4/2013 6:33 PM, Richard M. Heiberger wrote:
 >> tracebug and developer mode are fantastic additions to ESS.
 >> And yes, you can work inside a namespace.
 >> C-c C-t C-a mypackagename
 >> runs the command ess-developer-add-package
 >> This lets you put the revised function inside the namespace.
 >> My working pattern is to put the breakpoint in the function just before the
 >> current
 >> problematical statement and then single-line C-c C-n from there.  I can
 >> experiment inside
 >> a function until I am happy enough to enter Q
 >> and then C-c C-c the next revision of the function, with the breakpoint (if
 >> any) somewhere else.
 >> Rich
 > I tried ess-developer-add-package, and it seemed to work with one glitch.  The
 > glitch is that when the breakpoint came I got the browser() in the *R* window,
 > but there didn't seem to be the highlighted window with the current code and
 > line.  The unhighlighted version of the window was open and available.

That can only mean that R didn't report an error location. There might
be multiple reasons for that. It should never happen in the simplest
case when you evaluate a function definition.

If you have a reproducible example I can look into it.


More information about the ESS-help mailing list