From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: "Prus, Vladimir" <Vladimir_Prus@mentor.com>,
"Kozlov, Dmitry" <Dmitry_Kozlov@mentor.com>,
"gdb@sourceware.org" <gdb@sourceware.org>,
"Gustavo, Luis" <Luis_Gustavo@mentor.com>,
"Shebs, Stan" <Stan_Shebs@mentor.com>,
Marc Khouzam <marc.khouzam@ericsson.com>
Subject: Re: question on trace-stop-notes implementation
Date: Tue, 16 Oct 2012 16:38:00 -0000 [thread overview]
Message-ID: <507D8D6F.5090108@redhat.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2012-10-16 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 12:46 Dmitry Kozlov
2012-10-03 20:14 ` Stan Shebs
2012-10-07 8:00 ` Yao Qi
2012-10-07 17:26 ` Prus, Vladimir
2012-10-08 0:57 ` Yao Qi
2012-10-16 16:38 ` Pedro Alves [this message]
2012-10-17 1:16 ` Yao Qi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=507D8D6F.5090108@redhat.com \
--to=palves@redhat.com \
--cc=Dmitry_Kozlov@mentor.com \
--cc=Luis_Gustavo@mentor.com \
--cc=Stan_Shebs@mentor.com \
--cc=Vladimir_Prus@mentor.com \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=yao@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).