Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Support single step by arch or target
Date: Tue, 01 Sep 2015 14:40:00 -0000	[thread overview]
Message-ID: <83io7ucidu.fsf@gnu.org> (raw)
In-Reply-To: <1441096915-23615-3-git-send-email-yao.qi@linaro.org>

> From: Yao Qi <qiyaoltc@gmail.com>
> Date: Tue,  1 Sep 2015 09:41:55 +0100
> 
> gdb:
> 
> 2015-09-01  Yao Qi  <yao.qi@linaro.org>
> 
> 	* aarch64-linux-nat.c (aarch64_linux_can_do_single_step): New
> 	function.
> 	(_initialize_aarch64_linux_nat): Install it to to_can_do_single_step.
> 	* arm-linux-tdep.c (arm_linux_software_single_step): Return 0
> 	if target_can_do_single_step returns 1.
> 	* remote.c (struct vCont_action_support) <s, S>: New fields.
> 	(PACKET_vContSupported): New enum.
> 	(remote_protocol_features): New element for vContSupported.
> 	(remote_query_supported): Append "vContSupported+".
> 	(remote_vcont_probe): Remove support_s and support_S, use
> 	rs->supports_vCont.s and rs->supports_vCont.S instead.  Disable
> 	vCont packet if c and C actions are not supported.
> 	(remote_can_do_single_step): New function.
> 	(init_remote_ops): Install it to to_can_do_single_step.
> 	(_initialize_remote): Call add_packet_config_cmd.
> 	* target.h (struct target_ops) <to_can_do_single_step>: New field.
> 	(target_can_do_single_step): New macro.
> 	* target-delegates.c: Re-generated.
> 
> gdb/gdbserver:
> 
> 2015-09-01  Yao Qi  <yao.qi@linaro.org>
> 
> 	* server.c (vCont_supported): New global variable.
> 	(handle_query): Set vCont_supported to 1 if "vContSupported+"
> 	matches.  Append ";vContSupported+" to own_buf.
> 	(handle_v_requests): Append ";s;S" to own_buf if target supports
> 	hardware single step or vCont_supported is false.
> 	(capture_main): Set vCont_supported to zero.
> 
> gdb/doc:
> 
> 2015-09-01  Yao Qi  <yao.qi@linaro.org>
> 
> 	* gdb.texinfo (General Query Packets): Add vContSupported to
> 	tables of 'gdbfeatures' and 'stub features' supported in the
> 	qSupported packet, as well as to the list containing stub
> 	feature details.

OK for the documentation part.

Thanks.


  parent reply	other threads:[~2015-09-01 14:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01  8:42 [PATCH 0/2 V2] " Yao Qi
2015-09-01  8:42 ` [PATCH 2/2] " Yao Qi
2015-09-01 13:18   ` Antoine Tremblay
2015-09-01 14:23     ` Yao Qi
2015-09-01 15:30       ` Antoine Tremblay
2015-09-01 14:40   ` Eli Zaretskii [this message]
2015-09-04 14:46   ` Antoine Tremblay
2015-09-14  8:18     ` Yao Qi
2015-09-15 13:31   ` Pedro Alves
2015-09-01  8:42 ` [PATCH 1/2] [gdbserver] Rename supports_conditional_breakpoints to supports_hardware_single_step Yao Qi
2015-09-02 19:22   ` Antoine Tremblay
2015-09-03 15:13     ` Antoine Tremblay
2015-09-04 14:40       ` Antoine Tremblay
2015-09-04 15:04         ` Antoine Tremblay
2015-09-08 14:32     ` Yao Qi
2015-09-08 19:01       ` Antoine Tremblay
2015-09-09 15:37   ` Antoine Tremblay
2015-09-15 13:11 ` [PATCH 0/2 V2] Support single step by arch or target 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=83io7ucidu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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