diff options
| -rw-r--r-- | gdb/doc/ChangeLog | 11 | ||||
| -rw-r--r-- | gdb/doc/gdb.texinfo | 52 |
2 files changed, 52 insertions, 11 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 76d2c88..0e9fa3c 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,4 +1,15 @@ 2010-03-29 Stan Shebs <stan@codesourcery.com> + Nathan Sidwell <nathan@codesourcery.com> + + * gdb.texinfo (GDB/MI Tracepoint Commands): Add notes about the + GDBN equivalent. + (Set Tracepoints): Remove mention that conditional tracepoints + don't exist. + (Tracepoint Actions): Clarify when while-stepping collection + happens, note that while-stepping does not automatically collect + $pc. + +2010-03-29 Stan Shebs <stan@codesourcery.com> * gdb.texinfo (Tracepoint Packets): Describe QTDPsrc. (General Query Packets): Describe TracepointSource. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 57e4f03..ef51ed1 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -9334,10 +9334,10 @@ local variables, or global data. Later, you can use @value{GDBN} commands to examine the values these data had at the time the tracepoint was hit. -Tracepoints do not support every breakpoint feature. Conditional -expressions and ignore counts on tracepoints have no effect, and -tracepoints cannot run @value{GDBN} commands when they are -hit. Tracepoints may not be thread-specific either. +Tracepoints do not support every breakpoint feature. Ignore counts on +tracepoints have no effect, and tracepoints cannot run @value{GDBN} +commands when they are hit. Tracepoints may not be thread-specific +either. @cindex fast tracepoints Some targets may support @dfn{fast tracepoints}, which are inserted in @@ -9601,7 +9601,7 @@ recently defined (so that you can define a tracepoint and then say @code{actions} without bothering about its number). You specify the actions themselves on the following lines, one action at a time, and terminate the actions list with a line containing just @code{end}. So -far, the only defined actions are @code{collect} and +far, the only defined actions are @code{collect}, @code{teval}, and @code{while-stepping}. @cindex remove actions from a tracepoint @@ -9620,10 +9620,10 @@ In the following example, the action list begins with @code{collect} commands indicating the things to be collected when the tracepoint is hit. Then, in order to single-step and collect additional data following the tracepoint, a @code{while-stepping} command is used, -followed by the list of things to be collected while stepping. The -@code{while-stepping} command is terminated by its own separate -@code{end} command. Lastly, the action list is terminated by an -@code{end} command. +followed by the list of things to be collected after each step in a +sequence of single steps. The @code{while-stepping} command is +terminated by its own separate @code{end} command. Lastly, the action +list is terminated by an @code{end} command. @smallexample (@value{GDBP}) @b{trace foo} @@ -9674,7 +9674,7 @@ action were used. @kindex while-stepping @r{(tracepoints)} @item while-stepping @var{n} Perform @var{n} single-step instruction traces after the tracepoint, -collecting new data at each instruction. The @code{while-stepping} +collecting new data after each step. The @code{while-stepping} command is followed by the list of what to collect while stepping (followed by its own @code{end} command): @@ -9686,7 +9686,9 @@ command is followed by the list of what to collect while stepping @end smallexample @noindent -You may abbreviate @code{while-stepping} as @code{ws} or +Note that @code{$pc} is not automatically collected by +@code{while-stepping}; you need to explicitly collect that register if +you need it. You may abbreviate @code{while-stepping} as @code{ws} or @code{stepping}. @item set default-collect @var{expr1}, @var{expr2}, @dots{} @@ -26073,6 +26075,10 @@ frame. This field is present only if a trace frame was found. @end table +@subsubheading @value{GDBN} Command + +The corresponding @value{GDBN} command is @samp{tfind}. + @subheading -trace-define-variable @findex -trace-define-variable @@ -26087,6 +26093,10 @@ Create trace variable @var{name} if it does not exist. If trace variable to that value. Note that the @var{name} should start with the @samp{$} character. +@subsubheading @value{GDBN} Command + +The corresponding @value{GDBN} command is @samp{tvariable}. + @subheading -trace-list-variables @findex -trace-list-variables @@ -26115,6 +26125,10 @@ presently running. @end table +@subsubheading @value{GDBN} Command + +The corresponding @value{GDBN} command is @samp{tvariables}. + @subsubheading Example @smallexample @@ -26143,6 +26157,10 @@ Saves the collected trace data to @var{filename}. Without the in a local file. With the @samp{-r} option the target is asked to perform the save. +@subsubheading @value{GDBN} Command + +The corresponding @value{GDBN} command is @samp{tsave}. + @subheading -trace-start @findex -trace-start @@ -26156,6 +26174,10 @@ to perform the save. Starts a tracing experiments. The result of this command does not have any fields. +@subsubheading @value{GDBN} Command + +The corresponding @value{GDBN} command is @samp{tstart}. + @subheading -trace-status @findex -trace-status @@ -26209,6 +26231,10 @@ remaining space. These field is optional. @end table +@subsubheading @value{GDBN} Command + +The corresponding @value{GDBN} command is @samp{tstatus}. + @subheading -trace-stop @findex -trace-stop @@ -26222,6 +26248,10 @@ Stops a tracing experiment. The result of this command has the same fields as @code{-trace-status}, except that the @samp{supported} and @samp{running} fields are not output. +@subsubheading @value{GDBN} Command + +The corresponding @value{GDBN} command is @samp{tstop}. + @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% @node GDB/MI Symbol Query |