> Well, actually the documentation for "halt" says that an argument of 0 > should skip waiting for the halted state. This patch brings the code in > agreement with the doc.
Actually I find the documentation obtuse on this point. There is a difference between checking if the target was in the halted stated without waiting(which it does today) and not checking if the target is in the halted state. Checking if the target is in the halted stated *could* have side effects or even fail on some targets I guess. I'd favour clarifying the doc and a patch along your lines, except that I'd like to check for numeric 0 instead of string 0. This is to avoid annoying hard to trace bugs if the "halt 0" is e.g. generated via tcl in hex. Maybe that would "never happen", but I'd feel better if it parsed then argument to a number and checked afterwards. -- Øyvind Harboe PayBack incident management system Reduce costs and increase quality, free Starter Edition http://www.payback.no/index_en.html _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development