Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] traceframe_changed observer and MI notification
Date: Tue, 18 Sep 2012 08:48:00 -0000	[thread overview]
Message-ID: <50583505.9030006@codesourcery.com> (raw)
In-Reply-To: <83lig72206.fsf@gnu.org>

On 09/18/2012 04:01 PM, Eli Zaretskii wrote:
> Then that line should be deleted.
> 

OK.

>>> > >Also, I don't understand the significance of the reference to
>>> > >'tfind'.  Why is it important to mention that?
>>> > >
>> >
>> >because users use command 'tfind' to examine a certain traceframe, and
>> >the changes of traceframe trigger this MI notification, so I mention
>> >'tfind' here.
> The text you wrote can be interpreted as if using 'tfind' was the only
> way to change the trace frame.  If that's not true, 'tfind' it should
> be mentioned in parentheses, something like
> 
>    (e.g., by using the @code{tfind} command)

How about the new one?

-- 
Yao

gdb/doc:

	* observer.texi (GDB Observers): New observer 'traceframe_changed'.
	* gdb.texinfo (GDB/MI Async Records): Mention new MI notification
	'=traceframe-changed'.
gdb:

	* NEWS: Mention the new MI notification.
---
diff --git a/gdb/NEWS b/gdb/NEWS
index dba6937..126c2af 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -43,6 +43,8 @@ py [command]
 
   ** Command parameter changes are now notified using new async record
      "=cmd-param-changed".
+  ** Trace frame changes caused by command "tfind" are now notified using
+     new async record "=traceframe-changed".
 
 *** Changes in GDB 7.5
 
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index dc8860a..ee03521 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -27633,6 +27633,12 @@ thread group in whose context the library was unloaded.  If the field is
 absent, it means the library was unloaded in the context of all present
 thread groups.
 
+@item =traceframe-changed,num=@var{tfnum},tracepoint=@var{tpnum}
+@itemx =traceframe-changed,end
+Reports that the trace frame was changed and its new number is
+@var{tfnum}.  The number of the tracepoint associated with this trace
+frame is @var{tpnum}.
+
 @item =breakpoint-created,bkpt=@{...@}
 @itemx =breakpoint-modified,bkpt=@{...@}
 @itemx =breakpoint-deleted,id=@var{number}
diff --git a/gdb/doc/observer.texi b/gdb/doc/observer.texi
index c81e137..f682e9e 100644
--- a/gdb/doc/observer.texi
+++ b/gdb/doc/observer.texi
@@ -187,6 +187,13 @@ A tracepoint has been modified in some way.  The argument @var{tpnum}
 is the number of the modified tracepoint.
 @end deftypefun
 
+@deftypefun void traceframe_changed (int @var{tfnum}, int @var{tpnum})
+The trace frame is changed to @var{tfnum} (e.g., by using the
+@code{tfind} command).  The number of the tracepoint associated with
+this traceframe is @var{tpnum}.  If @var{tfnum} is negative, it means
+@value{GDBN} resumes live debugging.
+@end deftypefun
+
 @deftypefun void architecture_changed (struct gdbarch *@var{newarch})
 The current architecture has changed.  The argument @var{newarch} is
 a pointer to the new architecture.
---


  reply	other threads:[~2012-09-18  8:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-31  9:10 Yao Qi
2012-09-07  6:59 ` [ping]: " Yao Qi
2012-09-10 18:52 ` Tom Tromey
2012-09-11 13:38   ` Yao Qi
2012-09-11 15:28     ` Tom Tromey
2012-09-18  0:09 ` Yao Qi
2012-09-18  6:53   ` Eli Zaretskii
2012-09-18  7:24     ` Yao Qi
2012-09-18  8:01       ` Eli Zaretskii
2012-09-18  8:48         ` Yao Qi [this message]
2012-09-18  9:42           ` Eli Zaretskii
2012-09-18 11:42             ` 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=50583505.9030006@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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