I'm wondering if it would be a good idea to modify the handling of GDB halted/running state as follows:
- do nothing upon attaching GDB to OpenOCD. This gives the GDB init script more freedom w.r.t. what should happen when connecting to the target. - if the target is running and GDB is halted, then OpenOCD returns "white lies" in the register and memory queries. This allows users to issue a "monitor halt" or "stepi/continue" command after attaching to either halt the target or sync up with it. - When connecting to a halted target, the next stepi/continue returns immediately, thus allowing the register state to sync up to the current state of the target without modifying the state of the target - if, while GDB is halted, the target state changes behind GDBs back, then the next stepi/continue returns immediately to sync up GDB to the current state -- Øyvind Harboe Embedded software and hardware consulting services http://www.zylin.com _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
