From: "Abid, Hafiz" <hafiz_abid@mentor.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 7/7] range stepping: doc and NEWS
Date: Mon, 11 Mar 2013 13:38:00 -0000 [thread overview]
Message-ID: <1363009110.5561.1@abidh-ubunto1104> (raw)
In-Reply-To: <1363006291-13334-8-git-send-email-yao@codesourcery.com> (from yao@codesourcery.com on Mon Mar 11 12:51:31 2013)
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
>
>
next prev parent reply other threads:[~2013-03-11 13:38 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 12:52 [PATCH 0/7] Range stepping Yao Qi
2013-03-11 12:53 ` [PATCH 3/7] range stepping: gdbserver on x86/linux Yao Qi
2013-05-14 18:30 ` Pedro Alves
2013-05-15 7:40 ` Yao Qi
2013-05-20 18:00 ` Pedro Alves
2013-05-22 10:06 ` Yao Qi
2013-03-11 12:53 ` [PATCH 7/7] range stepping: doc and NEWS Yao Qi
2013-03-11 13:38 ` Abid, Hafiz [this message]
2013-03-11 17:01 ` Eli Zaretskii
2013-05-14 18:32 ` Pedro Alves
2013-03-11 12:53 ` [PATCH 2/7] Move rs->support_vCont_t to a separate struct Yao Qi
2013-03-11 12:53 ` [PATCH 5/7] range stepping: New command 'maint set range stepping' Yao Qi
2013-03-11 17:05 ` Eli Zaretskii
2013-03-18 3:10 ` Yao Qi
2013-03-18 5:39 ` Eli Zaretskii
2013-05-14 18:31 ` Pedro Alves
2013-03-11 12:53 ` [PATCH 6/7] range stepping: test case Yao Qi
2013-05-14 18:32 ` Pedro Alves
2013-05-15 8:27 ` Yao Qi
2013-05-20 18:29 ` Pedro Alves
2013-05-22 14:01 ` Yao Qi
2013-03-11 12:53 ` [PATCH 4/7] range stepping: gdb Yao Qi
2013-05-14 18:31 ` Pedro Alves
2013-05-15 8:07 ` Yao Qi
2013-05-20 17:59 ` Pedro Alves
2013-03-11 12:53 ` [PATCH 1/7] New macro THREAD_WITHIN_SINGLE_STEP_RANGE Yao Qi
2013-05-14 19:24 ` Pedro Alves
2013-03-14 20:12 ` [PATCH 0/7] Range stepping Pedro Alves
2013-03-15 19:54 ` Pedro Alves
2013-03-22 2:25 ` Yao Qi
2013-03-22 20:24 ` Pedro Alves
2013-04-11 6:16 ` [PATCH 0/7 V2] " Yao Qi
2013-04-11 6:17 ` [PATCH 1/7] New macro THREAD_WITHIN_SINGLE_STEP_RANGE Yao Qi
2013-04-11 6:17 ` [PATCH 2/7] Move rs->support_vCont_t to a separate struct Yao Qi
2013-04-11 6:18 ` [PATCH 3/7] range stepping: gdbserver on x86/linux Yao Qi
2013-04-11 6:19 ` [PATCH 4/7] range stepping: gdb Yao Qi
2013-04-11 13:22 ` Yao Qi
2013-04-12 12:35 ` Yao Qi
2013-04-11 6:19 ` [PATCH 5/7] range stepping: New command 'maint set range stepping' Yao Qi
2013-04-11 23:00 ` Eli Zaretskii
2013-04-11 6:38 ` [PATCH 6/7] range stepping: test case Yao Qi
2013-04-11 7:30 ` [PATCH 7/7] range stepping: doc and NEWS Yao Qi
2013-04-11 23:00 ` Eli Zaretskii
2013-04-12 20:48 ` [PATCH 0/7 V2] Range stepping Pedro Alves
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=1363009110.5561.1@abidh-ubunto1104 \
--to=hafiz_abid@mentor.com \
--cc=gdb-patches@sourceware.org \
--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