On Wed, Jan 13, 2010 at 9:17 AM, David Brownell wrote:
> On Tuesday 12 January 2010, Ųyvind Harboe wrote:
>> > Plus ... it can't be all that hard, just printf(string). ;)
>>
>> You mean: printf("%s", string) :-)
>
> What are you, paranoid that someone would put a '%..' format
> string in that Tcl
On Tuesday 12 January 2010, Øyvind Harboe wrote:
> > Plus ... it can't be all that hard, just printf(string). ;)
>
> You mean: printf("%s", string) :-)
What are you, paranoid that someone would put a '%..' format
string in that Tcl file, and cause a coredump?
On Wed, Jan 13, 2010 at 8:50 AM, David Brownell wrote:
> On Tuesday 12 January 2010, Øyvind Harboe wrote:
>> So I think the best thing is to be able to dump
>> the startup.tcl at this point then, it covers the line #'s
>> in stack traces.
>
> I certainly think that's the best solution all around,
On Tuesday 12 January 2010, Øyvind Harboe wrote:
> So I think the best thing is to be able to dump
> the startup.tcl at this point then, it covers the line #'s
> in stack traces.
I certainly think that's the best solution all around,
for that particular sub-problem.
A command-line flag would suff
So I think the best thing is to be able to dump
the startup.tcl at this point then, it covers the line #'s
in stack traces.
--
Ø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 programm
On Tuesday 12 January 2010, Øyvind Harboe wrote:
> > And it wouldn't create new headaches like ending up with
> > an old version of a discrete 'startup.tcl' ... or missing
> > any version whatsoever.
>
> Another thing that I was thinking about: how about using a
> startup.tcl on disk if it is ther
On Wed, Jan 13, 2010 at 7:08 AM, David Brownell wrote:
> On Tuesday 12 January 2010, Øyvind Harboe wrote:
>> > What happened to the idea of a command to print that
>> > embedded 'startup.tcl' file on demand?
>>
>> That does not address the problem of stack traces upon
>> errors during e.g. reset.
On Tuesday 12 January 2010, Øyvind Harboe wrote:
> > What happened to the idea of a command to print that
> > embedded 'startup.tcl' file on demand?
>
> That does not address the problem of stack traces upon
> errors during e.g. reset.
Right, there were several problems. You had fixes for
severa
> What happened to the idea of a command to print that
> embedded 'startup.tcl' file on demand?
That does not address the problem of stack traces upon
errors during e.g. reset.
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM
On Monday 11 January 2010, Øyvind Harboe wrote:
> IMHO, embedding into openocd executable is really the root
> cause of this misery in the first place.
It's a clean way to minimize dependencies on external files,
though... as in, eliminating installation bugs like "still
using the 'startup.tcl' ve
startup.tcl was split into one startup.tcl / module, which is nice.
However, this improvement made stack traces harder to read
as '"embedded:startup.tcl", line N' is now ambiguous.
Now if startup.tcl was just published together with the rest
of OpenOCD as any other script, that wouldn't be a prob
11 matches
Mail list logo
