From: "Prus, Vladimir" <Vladimir_Prus@mentor.com>
To: "Qi, Yao" <Yao_Qi@mentor.com>
Cc: "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: Sun, 07 Oct 2012 17:26:00 -0000 [thread overview]
Message-ID: <8815DDFC-F8BA-4C5C-BC00-7187CB58356C@mentor.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2012-10-07 17:26 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 [this message]
2012-10-08 0:57 ` Yao Qi
2012-10-16 16:38 ` Pedro Alves
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=8815DDFC-F8BA-4C5C-BC00-7187CB58356C@mentor.com \
--to=vladimir_prus@mentor.com \
--cc=Dmitry_Kozlov@mentor.com \
--cc=Luis_Gustavo@mentor.com \
--cc=Stan_Shebs@mentor.com \
--cc=Yao_Qi@mentor.com \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.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).