This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch 6/8] Agent's capability
- From: Pedro Alves <palves at redhat dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 10 Feb 2012 12:37:04 +0000
- Subject: Re: [patch 6/8] Agent's capability
- References: <4F1D55D7.7030506@codesourcery.com> <4F1D68A2.2080503@codesourcery.com> <4F3427EF.10906@redhat.com> <4F350CB6.80404@codesourcery.com>
On 02/10/2012 12:25 PM, Yao Qi wrote:
> On 02/10/2012 04:09 AM, Pedro Alves wrote:
>> That page is obsolete. We've been addressing those kinds of things with
>> qSupported features. I won't stand in the way of this change, but I do
>> wonder whether we shouldn't instead ask the agent about its features with
>> a similar (or exactly the same) mechanism.
>
> qSupported is used for GDB to get the list of features remote stub
> supports. However, agent can talk with GDB or GDBserver directly, so I
> hope GDB and GDBserver can use the same interface to get agent's
> capability. qSupported doesn't help here.
??? We have a way to sent commands to the agent, hence,
"I do wonder whether we shouldn't instead ask the agent about its
features with a similar (or exactly the same) mechanism.". Heck,
the agent itself could speak RSP, so we could just have gdb or gdbserver
forward it the tracepoint, breakpoint, etc packets.
Bit flags only allow on/off, and we'll run out of bits at some point. A
qSupported-like mechanism wouldn't have those issues. Just saying.
--
Pedro Alves