This is the mail archive of the gdb@sourceware.org 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: multi-proc: info processes?

From: Michael Snyder <msnyder at vmware dot com>
To: Stan Shebs <stan at codesourcery dot com>
Cc: "pedro at codesourcery dot com" <pedro at codesourcery dot com>, "gdb at sourceware dot org" <gdb at sourceware dot org>
Date: Wed, 12 Nov 2008 13:21:59 -0800
Subject: Re: multi-proc: info processes?
References: <491B3695.5090300@vmware.com> <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?

Follow-Ups:
- Re: multi-proc: info processes?
  - From: Pedro Alves

References:
- multi-proc: info processes?
  - From: Michael Snyder
- Re: multi-proc: info processes?
  - From: Stan Shebs

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