Re: Proposal for customization of output of "to_pid_to_str" op in remote.c

[Daniel Jacobowitz <drow@mvista.com>]

On Wed, Dec 11, 2002 at 02:51:46PM -0800, Nat Gurumoorthy wrote:
> >Daniel Jaccobowitz wrote
> >The remote protocol allows you to return more information in the stub. 
> >Can you do that instead?  See ThreadExtraInfo.
> 
> Daniel,
>     I know that. Just as the remote protocol allows me to print out
> extra information about each thread, I would like it to let me print
> out the name of the thread and not call it "Thread 1" or "Thread 2"
> etc. The proposed interface will allow the target dependent layer
> to print what ever it wants. If the target dependent layer does not
> specify the macro the behavior reverts to the Original mode.
> 
> Regards
> Nat
> 
> ps: Thanks for pointing out the problem with the natg@ubicom.com address.
> It has been fixed.

What's wrong with:
1  Thread 1 (Original thread)
2  Thread 2 (Extra thread)
3  Thread 4 (Thread I Felt Like)
?  What output do you want?  I'd like to keep it printing the TID for
consistency.

In any case, a target macro the way you did this is probably the wrong
way.  It looks almost like you want a gdbarch method...

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer