This is the mail archive of the
mailing list for the GDB project.
Re: [patch 5/8] Doc for agent
- 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 15:01:26 +0000
- Subject: Re: [patch 5/8] Doc for agent
- References: <4F1D55D7.firstname.lastname@example.org> <4F1D678B.email@example.com> <4F34248A.firstname.lastname@example.org> <4F351BC1.email@example.com>
On 02/10/2012 01:29 PM, Yao Qi wrote:
> On 02/10/2012 03:54 AM, Pedro Alves wrote:
>> Some things, like the new target-side breakpoint conditions, and tracepoints,
>> use agent expressions as well, without having an agent loaded in the inferior.
>> Do you think it still makes sense to move the whole section considering that?
> No, I don't think it makes sense anymore, because agent expression is being
> used in non-agent cases. My patch should be updated as well. We
> can add a new chapter for "Agent", which is about how to control
> agent by commands, and leave original appendix GDB Agent Expression
> Mechanism there, with some minor changes, where needed. WDYT?
Re. "control agent by commands". So you're planning on making the agent speak
some other command set other than RSP? I'd think that making it talk exactly
RSP would be the best, since #1, you need some kind of command set anyway;
#2, the agent should be able to support debugging (stepping, breakpoints,
etc.) without gdbserver involved, and for that you'd want to support
the RSP anyway so that GDB can connect. Unless you're coming up with some
new rpc/marshaling protocol that's clearly superior to RSP?