This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: question on trace-stop-notes implementation
- From: Pedro Alves <palves at redhat dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: "Prus, Vladimir" <Vladimir_Prus at mentor dot com>, "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: Tue, 16 Oct 2012 17:38:07 +0100
- Subject: Re: question on trace-stop-notes implementation
- References: <506C3395.8010701@mentor.com>,<5071367F.4030203@codesourcery.com> <8815DDFC-F8BA-4C5C-BC00-7187CB58356C@mentor.com> <507224D8.5000902@codesourcery.com>
On 10/08/2012 01:56 AM, Yao Qi wrote:
> 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,
I don't think that's the same issue. If you connect to a target that already had
tracing on progress, you'd want to read the stop note that was already set on the
target. There's no way currently. With RSP notifications, and MI change notifications
in place, you'd still miss a way to sync the stop note on initial connection.
--
Pedro Alves