From: Michael Snyder <msnyder@vmware.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: "pedro@codesourcery.com" <pedro@codesourcery.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: multi-proc: info processes?
Date: Wed, 12 Nov 2008 21:22:00 -0000 [thread overview]
Message-ID: <491B48F7.5030407@vmware.com> (raw)
In-Reply-To: <491B3A6E.5010208@codesourcery.com>
Stan Shebs wrote:
> Michael Snyder wrote:
>> Hey Pedro,
>>
>> For your multi-process work, are you planning anything
>> analogous to the "info threads" command, eg. "info processes"?
> Look at "info inferiors". It's just the processes (or whatever) that are
> currently being controlled by GDB.
>> What might that look like, in your model? Would it list,
>> say, just the processes that gdb is attached to? Or would
>> you want something analogous to "ps", that would list all
>> of the processes that are available to be attached?
> That would be somewhat ambitious, especially for a remote target - I
> think you'd need a new packet just to return the list of processes...
Sure -- by analogy with qfThreadInfo/qsThreadInfo, it could
be implemented as an iterator.
I'm not sure how desireable it is, but it could save you
from having to go over to the remote target and typing "ps"...
By the way, what about remote attach? Is that in the plan?
next prev parent reply other threads:[~2008-11-12 21:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 20:04 Michael Snyder
2008-11-12 20:20 ` Stan Shebs
2008-11-12 20:51 ` Vladimir Prus
2008-11-12 21:22 ` Michael Snyder [this message]
2008-11-12 21:30 ` Pedro Alves
2008-11-12 23:16 ` Michael Snyder
2008-11-13 1:48 ` Michael Snyder
2008-11-13 4:57 ` Daniel Jacobowitz
2008-11-13 8:09 ` EBo
2008-11-13 8:21 ` Vladimir Prus
2008-11-13 23:19 ` Michael Snyder
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=491B48F7.5030407@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=stan@codesourcery.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