this change also fixed a raft of strange and hard to reproduce bugs. E.g. GDB could get stuck breakpoints upon connect from a previous session that was terminated ungracefully.
On Sun, Aug 24, 2008 at 6:17 PM, Dominic <[EMAIL PROTECTED]> wrote: > Just found this post when I was looking for arm7_9 force_hw_bkpts. > > - How is one supposed to force the use of hardware breakpoints, for example > when debugging via insight? help gdb_override Also openocd.texi documents obsolete commands. > - How are software breakpoints handled in the absence of the arm7_9 sw_bkpts > command? The old behaviour was to disable software breakpoints by default on > targets that required the use of a watchpoint unit (ARMv4, e.g. ARM7TDMI) and > enable them on hardware supporting the BKPT instruction (ARMv5, e.g. > ARM926EJ-S). just add a software breakpoint and if a hw breakpoint is available to implement the sw breakpoint, you get a sw breakpoint, otherwise you get an error message. > Maybe it would have been better to discuss these changes after the list was up > again, to give people actually a chance to send feedback... I did get feedback from Spen. Also it was a judgement call to fix bugs before berlios was back up and running. We didn't have an ETA on a working mailing list. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
