On Thu, Jun 17, 2010 at 12:30 AM, Øyvind Harboe <[email protected]> wrote: > On Wed, Jun 16, 2010 at 11:40 PM, Andreas Fritiofson > <[email protected]> wrote: >> >> The stack trace provides no valuable information to the user for >> interactive commands. > > What about nested proc's? >
You mean when calling user defined tcl procedures calling other tcl procedures that fails? My guess is the *user* doesn't particularly care about the chain of events leading up to the fault. It's probably due to either misuse of the first procedure, in which case the user is fully aware of what the called procedure was, or a bug in one of the following. If it's a bug it calls for debugging, a job for a *developer* (might of course be the same person with another hat). The developer could flip the debug level switch and see the stack trace as previously. Then on the other hand I don't get a stack trace when a shell script in multiple nesting levels fails, and I'm not very bothered about that. I think the current error messages do more harm than good in the majority of cases. If there's a better solution I'm open to suggestions. /Andreas _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
