From: Vladimir Prus <vladimir@codesourcery.com>
To: "Marc Khouzam" <marc.khouzam@ericsson.com>
Cc: gdb@sources.redhat.com
Subject: Re: Multiprocess MI extensions
Date: Tue, 17 Jun 2008 19:50:00 -0000 [thread overview]
Message-ID: <200806172350.02564.vladimir@codesourcery.com> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA042911E5@ecamlmw720.eamcs.ericsson.se>
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
next prev parent reply other threads:[~2008-06-17 19:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 19:24 Vladimir Prus
2008-06-10 19:42 ` Pawel Piech
2008-06-10 19:53 ` Vladimir Prus
2008-06-11 16:40 ` Pawel Piech
2008-06-11 16:43 ` Vladimir Prus
2008-06-13 17:34 ` Marc Khouzam
2008-06-14 15:15 ` Vladimir Prus
2008-06-17 18:32 ` Marc Khouzam
2008-06-18 8:39 ` Vladimir Prus
2008-06-18 13:49 ` Marc Khouzam
2008-06-17 19:28 ` Marc Khouzam
2008-06-17 19:33 ` Marc Khouzam
2008-06-17 19:50 ` Vladimir Prus [this message]
2008-06-17 20:19 ` Marc Khouzam
2008-06-18 7:41 ` Vladimir Prus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200806172350.02564.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=gdb@sources.redhat.com \
--cc=marc.khouzam@ericsson.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox