Re: [patch:MI] Observer for thread-changed

[Pedro Alves <pedro@codesourcery.com>]

A Tuesday 10 June 2008 03:03:46, Nick Roberts wrote:
>  > It all amounts to:
>  >
>  >  - should there be an MI async event on -thread-select if the
>  >    reply already carries that information?
>
> But the CLI command "thread" doesn't.  I think MI should try to reflect the
> state of GDB and the inferior.  It shouldn't really matter what commands
> were used to put it in that state.

I see.  I hadn't thought of CLI in MI.  Thanks.

> If it goes at the end of do_captured_thread_select then I guess that will
> be after any exceptions but, to me, putting the logic in gdb_thread_select
> makes it clearer that the thread only gets reported when there is no
> exception.

I think it's clearer to put the observer close to where to switch
is performed.  Plus, if/when we remove libgdb and the wrapper, we
have again to move the observer call... Not the end of the world, but
might as well put it in the right place now, IMHO.  Oh well, opinions :-)  

-- 
Pedro Alves