Re: [PATCH 7/7] range stepping: doc and NEWS

Abid, Hafiz
2013-03-11T13:38:42Z

On 11/03/13 12:51:31, Yao Qi wrote:
> gdb/doc:
>
> 2013-03-11 Yao Qi <yao@codesourcery.com>
>
> * gdb.texinfo (Packets): Document about 'vCont;r'.
>
> gdb:
>
> 2013-03-11 Yao Qi <yao@codesourcery.com>
>
> * NEWS: Mention range stepping, new packet and new
> commands.
> ---
> gdb/NEWS | 12 ++++++++++++
> gdb/doc/gdb.texinfo | 5 +++++
> 2 files changed, 17 insertions(+), 0 deletions(-)
>
> diff --git a/gdb/NEWS b/gdb/NEWS
> index 99b8add..836638c 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -89,6 +89,10 @@ catch signal
> maint info bfds
> List the BFDs known to GDB.
>
> +maint set range-stepping
> +maint show range-stepping
> + Control and show whether do range stepping.
What about having a to here. ^^

> +
> python-interactive [command]
> pi [command]
> Start a Python interactive prompt, or evaluate the optional command
> @@ -164,11 +168,19 @@ show filename-display
> feature to be enabled. For more information, see:
> http://fedoraproject.org/wiki/Features/MiniDebugInfo
>
> +* GDB now supports range stepping, which improves the performance of
> + single stepping over a source line by reducing the number of
> control
> + packets from GDB.
> +
> * New remote packets
>
> QTBuffer:size
> Set the size of trace buffer. The remote stub reports support
> for this
> packet to gdb's qSupported query.
> +vCont;r
> + Tell the remote stub to do range stepping in an address range.
> The remote
> + stub reports a stop reply when the program goes out of the range
> or is
> + stopped due to other reasons, such as hitting a breakpoint.
>
> *** Changes in GDB 7.5
>
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index 7c06120..b505cda 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -36261,6 +36261,11 @@ Step.
> Step with signal @var{sig}. The signal @var{sig} should be two hex
> digits.
> @item t
> Stop.
> +@item r @var{start},@var{end}
> +Step repeatedly while the PC is within the range [@var{start},
> +@var{end}). Note that a stop reply may be sent at any point even if
> +the PC is within the stepping range; for example, it is permissible
> to
> +implement this packet in a degenerate way as a single step operation.
> @end table
>
> The optional argument @var{addr} normally associated with the
> --
> 1.7.7.6
>
>