George Neuner <gneuner2/@/comcast.net> wrote:
| Rainer Joswig <email@example.com> wrote:
| > George Neuner <gneuner2/@/comcast.net> wrote:
| >> I've rarely found back traces useful other than to tell me what
| >> function calls led to the problem. I've never seen a back trace that
| >> included enough information to recreate the problem so I can step
| >> through and watch.
| >I don't use stepping much, but I use backtraces all the time.
| Like I said, I've found backtraces rarely include enough information
| to debug a complicated problem. They end up just pointing me in the
| right direction.
To use backtraces most profitably [for more than just a static
announcement that there *is* a problem in some area] you need to
be in your CL's debugger where, armed with the backtrace, you
can move up and down the stack frames, examining local variables,
looking at the corresponding source files, executing little bits
of interactively designed test code, etc.
Rob Warnock <firstname.lastname@example.org>
627 26th Avenue <URL:http://rpw3.org/>
San Mateo, CA 94403 (650)572-2607