Skip to content
Prev 26890 / 63434 Next

trace() problems (PR#10498)

The problem is at least as old as 2.5.1.  Looks like a line disappeared 
from trace(), something like:
    on.exit(tracingState(tState))

As a result, if an error occurs in the call to trace(), the tracing 
state is left FALSE.  The workaround is to turn it on explicitly:

    tracingState(TRUE)

after which normal behavior should resume.
murdoch at stats.uwo.ca wrote: