This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: question on trace-stop-notes implementation
- From: "Prus, Vladimir" <Vladimir_Prus at mentor dot com>
- To: "Qi, Yao" <Yao_Qi at mentor dot com>
- Cc: "Kozlov, Dmitry" <Dmitry_Kozlov at mentor dot com>, "gdb at sourceware dot org" <gdb at sourceware dot org>, "Gustavo, Luis" <Luis_Gustavo at mentor dot com>, "Shebs, Stan" <Stan_Shebs at mentor dot com>, Marc Khouzam <marc dot khouzam at ericsson dot com>
- Date: Sun, 7 Oct 2012 17:26:01 +0000
- Subject: Re: question on trace-stop-notes implementation
- References: <506C3395.8010701@mentor.com>,<5071367F.4030203@codesourcery.com>
Does that work if we connect to a target that has tracing in progress, with some end note already set?
- Volodya
On 07.10.2012, at 12:00, "Yao Qi" <yao@codesourcery.com> wrote:
> On 10/03/2012 08:46 PM, Dmitry Kozlov wrote:
>> This provides difficulties for IDE integration: for exampe IDE can't
>> know that stop notes changed without explicit quering gdb by show
>> stop-notes.
>
> A new MI notification 'command param changed' was added to GDB CVS
> mainline some weeks ago, and MI frontend should get the notification when stop note is changed by 'set trace-stop-notes' command.
>
> (gdb)
> set trace-stop-notes bar
> &"set trace-stop-notes bar\n"
> =cmd-param-changed,param="trace-stop-notes",value="bar"
> ^done
>
> This notification (along with other notifications I added recently) is to address the difficulties you mentioned (MI frontend has to query GDB to get some states of GDB).
>
> --
> Yao