info thread

Daniel Jacobowitz wrote:

>On Sat, Sep 23, 2006 at 09:05:56PM +0200, Mark Kettenis
wrote:
>  
>
>>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.
>>    
>>
>
>Except as strings, presumably?
>
>It's supposed to be useful to users; the extra
information is supposed
>to be exactly what would be useful in a dialog box
listing threads.
>
Some GDB target displays thread priority and some usefull
information in 
that string.
In ST we display the thread's name for some targets for
instance.
I think we must keep it either in MI command
-thread-list-all-threads or 
in a new MI command.



About current thread, it is displayed by an asterisk with
"info thread" 
command, and gathered by Eclipse today from that output,
, whereas it could be from the  MI stop reply message.

Do we need to have the current thread ID in one of the
-thread-blabla 
command ?
That would avoid storing it somewhere in the GUI.

Denis

On Mon, Sep 25, 2006 at 04:49:07PM +0200, Denis PILAT wrote:
> About current thread, it is displayed by an asterisk
with "info thread" 
> command, and gathered by Eclipse today from that
output,
> , whereas it could be from the  MI stop reply message.
> 
> Do we need to have the current thread ID in one of the
-thread-blabla 
> command ?
> That would avoid storing it somewhere in the GUI.

I think this would be a good idea, since it would be so
easy.  It will
be simpler for consumers.  They should be able to keep track
of it
by watching stop replies and their own -thread-select
commands, and
some future notifier support for e.g. typing "thread
2" at a console,
but there's no reason to make this hard.

-- 
Daniel Jacobowitz
CodeSourcery