My program is generating this:
I don’t know which spot is causing this, or the call tree. I would like to start the tracer when an error occurs so I can examine where it’s at. trace_on_error does not seem to be a predicate though. For what it’s worth, there are more than one catch calls in this stack, so some suggestions are not viable, and setting debug=true for the duration is also not always viable, though sometimes it is.