This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PING] [RFC-v3] Add windows Thread Information Block
- From: Daniel Jacobowitz <dan at codesourcery dot com>
- To: Pierre Muller <pierre dot muller at ics-cnrs dot unistra dot fr>
- Cc: 'Pedro Alves' <pedro at codesourcery dot com>, gdb-patches at sourceware dot org
- Date: Wed, 10 Mar 2010 18:30:40 -0500
- Subject: Re: [PING] [RFC-v3] Add windows Thread Information Block
- References: <000901c9f5ef$4ee06f10$eca14d30$@u-strasbg.fr> <20090703194220.GA30668@ednor.casa.cgf.cx> <002901cac075$1f8f44b0$5eadce10$@muller@ics-cnrs.unistra.fr> <201003101725.48298.pedro@codesourcery.com> <000c01cac0a0$3935fbe0$aba1f3a0$@muller@ics-cnrs.unistra.fr>
On Wed, Mar 10, 2010 at 11:22:51PM +0100, Pierre Muller wrote:
> OK, I start to remember now,
> you said that TARGET_OBJECT_DATA should use xml syntax for
> all data transmission, what that it?
My two cents... the issue isn't that you aren't using XML, but that
you're using TARGET_OBJECT_OSDATA. That's for information about the
operating system, like the list of all running processes, not about
the current process.
Pedro, this raises an interesting question. Suppose Pierre added a
new qXfer object. How would he indicate to a remote target which
process's object was requested? This may be something already
handled, but I don't know the answer.
--
Daniel Jacobowitz
CodeSourcery