On Wed, Jan 13, 2010 at 7:08 AM, David Brownell <davi...@pacbell.net> 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. > > Right, there were several problems. You had fixes for > several of them. > > An "dump_startup" command (or commandline option) would > give the file, from which line numbers are easily got.
Ah. Right. Didn't think of that. > 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 there? That would also remove the most urgent need for dumping the builtin startup.tcl. There are LOTS of files that openocd ships with that users can depend on, startup.tcl isn't *that* special. -- Ø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-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
