One problem with GDB is that it can get out of sync with the target. While GDB believes that the target is in the halted mode, the target could be running, powered down, halted, etc.
Here is an idea: - add a new command to OpenOCD, "sync". When this is issued on a target, the next step command will be a no-op. - when needing to sync up GDB to the target state, issue a "monitor sync" + "stepi". A similar scheme would be required for attaching to OpenOCD as GDB is trying to halt the target upon connection. OpenOCD would then issue an implicit "sync" upon attaching to the target. GDB will query the target for the register values after connect, upon which it is told white lies today. A "stepi" immediately after connecting GDB to OpenOCD would then be required to sync up GDB to the target state.... Thoughts? -- Øyvind Harboe Embedded software and hardware consulting services http://www.zylin.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
