This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA] Report the main thread.

Nick Roberts wrote:

>  > >> Will some approach that only produce MI output be fine with you?
>  > > 
>  > > Perhaps that means any observer for a new MI thread should go in
>  > > add_thread_silent?
>  > 
>  > Yes, moving the observer call to add_thread_silent is the most
>  > direct approach to make MI work the way I want without disturbing CLI.
> I still don't see the point in reporting the main thread.  If there's more
> than one thread the user can switch between them but what course of action
> is available with just one thread?

What is the purpose of =thread-created? Presumably, this is to allow
the frontend to keep up-to-date list of threads without doing -thread-info.
For that to be possible, it's necessary that for every single thread in
the output of -thread-info, there's also =thread-created.

Of course, a frontend might decide to use -thread-info most of the time,
and use =thread-create to update the list only when the target is running,
in which case reporting the main thread might be less critical. But still,
it seems more consistent to report main thread, as long as -thread-info
includes it.

- Volodya

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]