This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: question on trace-stop-notes implementation
- From: Yao Qi <yao at codesourcery dot com>
- To: "Prus, Vladimir" <Vladimir_Prus 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: Mon, 8 Oct 2012 08:56:56 +0800
- Subject: Re: question on trace-stop-notes implementation
- References: <506C3395.8010701@mentor.com>,<5071367F.4030203@codesourcery.com> <8815DDFC-F8BA-4C5C-BC00-7187CB58356C@mentor.com>
On 10/08/2012 01:26 AM, Prus, Vladimir wrote:
Does that work if we connect to a target that has tracing in progress, with some end note already set?
Yes, I think so. Command parameter change notification is emitted
whenever command parameter is changed, it has nothing to do with other
factors.
The session below is about what you want, IIUC,
(gdb)
set trace-stop-notes foo
&"set trace-stop-notes foo\n"
=cmd-param-changed,param="trace-stop-notes",value="foo"
^done
(gdb)
tstart
&"tstart\n"
=tracepoint-downloaded,id="1",address="0x080483ca"\n
^done
(gdb)
set trace-stop-notes bar
&"set trace-stop-notes bar\n"
=cmd-param-changed,param="trace-stop-notes",value="bar"
^done
--
Yao