This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: info thread
> Date: Tue, 19 Sep 2006 17:03:16 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> This isn't really relevant. It breaks down into just a few parts in GDB
> parlance:
>
> - The GDB ID. That's "1", "2", et cetera in your example.
> - The thread ID, produced by to_pid_to_str, e.g. "Thread -BLAH (LWP
> BLAH)". This is just a string.
> - The thread extra info. Not present in your example, but e.g.
> "(Exiting)" or "(not ready)".
> - The thread's current stack frame.
>
> That last, I think, is not useful in MI. There's commands to fetch it
> when it's wanted, and it might not be by some consumers. And it will
> show up with -thread-select already. So, I would recommend including
> only the GDB ID (as from -thread-list-ids) and the additional
> information.
Note that the formatting of the thread ID produced by to_pid_to_str is
highly dependent on the specific threads model in use. The thread
extra info is also mostly free-form. That means it might not be wise
to export that information in the MI interface.
Mark