RE: Multiprocess MI extensions

["Marc Khouzam" <marc dot khouzam at ericsson dot com>]

As for the output of -list-thread-groups 

>   ^done,result={threads=[<thread>],groups=[<group>]}
> where each thread group is like this:
>   {id="xxx",type="process",pid="yyy",num_children="1"}

I'm not clear on the "threads" part of the output.
Will that part only be filled if we issue 
-list-thread-groups GROUP
where GROUP is a process and therefore only has threads as children?

If that is the case, then "threads" and "groups" cannot both
have content at the same time, right?

Further, I guess this would mean we can use -list-thread-groups
all the time, and no longer use -thread-list-ids?

Is this what you meant?

Thanks

marc


> -----Original Message-----
> From: Vladimir Prus [mailto:vladimir@codesourcery.com]
> Sent: Tuesday, June 17, 2008 3:50 PM
> To: Marc Khouzam
> Cc: gdb@sources.redhat.com
> Subject: Re: Multiprocess MI extensions
> 
> 
> On Tuesday 17 June 2008 23:33:49 Marc Khouzam wrote:
> > Sorry, I was too quick on this one.
> > 
> > > > >> 4. The -list-thread-groups will accept the '--available' 
> > > > option that tells
> > > > >> it to list all thread groups, including those that are not 
> > > > attached to yet.
> > > 
> > > I assume this will list all top-level thread groups, but not their
> > > chidren, right?
> > 
> > Actually, is the behavior going to be like this:
> > 
> > /*
> >  *    -list-thread-groups [--available] [GROUP]
> >  *
> >  * With no arguments, produces a list of the top-level 
> thread groups to which GDB 
> >  * is attached.
> >  * If a group id is specified, produces a list of groups to 
> which GDB is attached
> >  * and that are children of the specified group.
> >  * With --available, same as above, but produces a list of 
> all thread groups 
> >  * instead of only the ones GDB is attached to.
> >  */
> 
> Right, that's what I meant.
> 
> - Volodya
>