Much better!
Merged.
Thanks!
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-development mailing list
Openocd-de
On Thu, Jun 17, 2010 at 7:24 AM, Øyvind Harboe wrote:
> On Thu, Jun 17, 2010 at 2:05 AM, Andreas Fritiofson
> wrote:
>> On Thu, Jun 17, 2010 at 12:30 AM, Øyvind Harboe
>> wrote:
>>> On Wed, Jun 16, 2010 at 11:40 PM, Andreas Fritiofson
>>> wrote:
The stack trace provides no valuable i
On Thu, Jun 17, 2010 at 2:05 AM, Andreas Fritiofson
wrote:
> On Thu, Jun 17, 2010 at 12:30 AM, Øyvind Harboe
> wrote:
>> On Wed, Jun 16, 2010 at 11:40 PM, Andreas Fritiofson
>> wrote:
>>>
>>> The stack trace provides no valuable information to the user for
>>> interactive commands.
>>
>> What a
On Thu, Jun 17, 2010 at 12:30 AM, Øyvind Harboe wrote:
> On Wed, Jun 16, 2010 at 11:40 PM, Andreas Fritiofson
> 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
On Wed, Jun 16, 2010 at 11:40 PM, Andreas Fritiofson
wrote:
>
> The stack trace provides no valuable information to the user for
> interactive commands.
What about nested proc's?
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 AR
The stack trace provides no valuable information to the user for
interactive commands. If debug output isn't enabled, print the command
result as a regular error message instead of using Jim's stacktrace
feature. This has the added benefit that syntax errors are properly marked
as such in the log.
