On Wed, Jul 16, 2008 at 10:34 AM, Spen <[EMAIL PROTECTED]> wrote:
>>
>> Committed improved error messages.
>>
>
> Thanks seems to fix that one.
>
> Still seem to have a few outstanding issues.
>
> when running the shutdown command we get
> Debug:   462 1125 command.c:399 command_run_line_internal(): "shutdown"
> Info:    463 1125 options.c:50 configuration_output_handler(): Runtime
> error, file "?", line 8:
> Info:    464 1125 options.c:50 configuration_output_handler():
> Info:    465 1125 options.c:50 configuration_output_handler(): In procedure
> 'unknown' called at file "?", line 1
> Info:    466 1125 options.c:50 configuration_output_handler(): In procedure
> 'shutdown' called at file "debug.script", line 4
> Info:    467 1125 options.c:50 configuration_output_handler(): In procedure
> 'target_post_reset_0' called at file "?", line 1

This looks ugly, but is it wrong?

To make error messages/stack traces from Jim Tcl prettier is
definitely one of the things that needs to be fixed before this is
ready for prime-time.

The other problem is that OpenOCD is using error codes(exceptions
esentially), to communicate that a shutdown was requested.



> also if we run a openocd command such as flash info (with missing arg),
> openocd would normally return with the expected command line.
> now we get

fixed:

> flash info
flash info                print info about flash bank <num>
Runtime error, file "?", line 5:

In procedure 'flash' called at file "?", line 1


>> flash info
> Runtime error, file "?", line 5:
>
> In procedure 'flash' called at file "?", line 1
>
> for my use i am starting to miss the old interpreter - at least i could
> debug it.

I don't know what to say to that.

We have made great strides in adding scripting support, but it
still sucks in places.

Making it easier to debug is also a goal, where we've made
progress.


-- 
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to