Hi, currently, commands like "reg" or "mdw" return an empty string when using in TCL scripting:
> reg pc pc (/32): 0x000011E0 > set pc [reg pc] pc (/32): 0x000011E0 > echo $pc > I tried a quick hack for "reg" and it seemed to work in the beginning, but later OpenOCD crashed on invalid pointers. My questions: - is there an *easy* way to provide the OpenOCD command output as a TCL string as well? Like repeating the last output string of the internal commands? Reworking the interfaces from .handler to .jim_handler is no fun ... - would it make sense to restrict information in the returned TCL strings to the "right stuff", e.g. only the hex value of the register or dumped memory cell? Best regards, Alex ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
