On Thu, Mar 23, 2017 at 11:40 AM, Freddie Chopin <[email protected]>
wrote:
> On Thu, 2017-03-23 at 11:34 +0000, Yao Qi wrote:Providing
> > thread info isn't just printing thread name and state in "info
> > threads". GDB internally needs thread information too.
>
> But that's all GDB is getting from OpenOCD - thread name (string),
> extra info (string) and stack frame (registers).
>
> Unless I'm missing something, which is of course possible (;
>
There's a bit more to it than that, but that's what users see most often.
It's important to point out that GDB's remote target support isn't the
best; it's not on par with a local target by any means. It wasn't until
recently that thread names could be assigned/sign for remote targets
(7.11.2 IIRC). To the OP, if you're interested in extending behavior, I'd
suggest starting with a small PoC. I think you'll get a better idea of the
issues at hand once you start exploring the GDB source.
Steve
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
