This looks good to me. I'm not sure what a good long term solution might be.
A requirement/goal of OpenOCD is that it should "just work" with the default settings when using "monitor" commands w/GDB. Really this warning is a reminder to OpenOCD developers to fix the code so "monitor XXX" commands and the like do not cause errors with the default "set remotetimeout 2" that GDB has. OpenOCD is currently single threaded so sending keep alive messages is tedious... pthreads is a new can of works entirely, but perhaps it *would* be a good idea introduce some multithreaded capabilities in OpenOCD? -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
