Mathias K. wrote: > > When I make gdb attach to OpenOCD I *always* want gdb to have control > > over the target CPU. > > This is already done with the gdb monitor command.
As you know this *isn't* done. That is the point. Yes OpenOCD can be controlled from within gdb, that's not the point. The point is that it is lame that gdb is *ever* out of sync with OpenOCD. Extremely lame. I don't know how to fix it unfortunately. //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 OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
