Re: New mi commands for threads

Denis PILAT
2007-03-19T13:45:24Z

Nick Roberts wrote:
> > This output is a side effect of the frame printing, the actual
> > -thread-select command has the same. I'm going to have a look at how we
> > can avoid it, but I think it will impact *-thread-select* as well.
>
> OK, I dodn't realise that. Interestingly the example in the manual doesn't
> show the duplicate information (or the fullname field, so it will have to be
> updated). It seems to due to the fact that do_captured_thread_select uses
> SRC_AND_LOC, while the other MI commands use LOC_AND_ADDRESS. I see that
> normal_stop specifies LOC_AND_ADDRESS specifically for MI. It looks a bit
> of a hack but perhaps we should do the same for do_captured_thread_select:
>
> /* For mi, have the same behavior every time we stop:
> print everything but the source line. */
> if (ui_out_is_mi_like_p (uiout))
> source_flag = LOC_AND_ADDRESS;
>
>
>
Right,
I'm going to propose a separate patch for that right now.

Then I'll do the same for -thread-info new command.

Denis