James Zhao wrote: > So it would seems that when gdb_new_connection is invoked, there is not > check if device is halted or not. > And this become a problem when trying to get register since the device > needed to be halted first. > Is there a good place in the code to add a check for device halt, when > gdb_new_connection is called?
In principle I agree with the proposed patchset, but in practise I'm not sure where it should go. When I make gdb attach to OpenOCD I *always* want gdb to have control over the target CPU. This isn't the case if the CPU is running, and I must fiddle with continue and Ctrl-C to get into a reliable synchronised state. Lame! Halting on gdb connect is indeed one way to change that - but I'm not sure it's the right way. Another way would be to make gdb always issue a halt. I'm not sure what semantics gdb uses for remotes. //Peter ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
