Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 06/18] New vCtrlC packet, non-stop mode equivalent of \003
Date: Mon, 26 Oct 2015 14:11:00 -0000	[thread overview]
Message-ID: <86io5t26rr.fsf@gmail.com> (raw)
In-Reply-To: <1444836486-25679-7-git-send-email-palves@redhat.com> (Pedro	Alves's message of "Wed, 14 Oct 2015 16:27:54 +0100")

Pedro Alves <palves@redhat.com> writes:

> gdb/
> 2015-10-14  Pedro Alves  <palves@redhat.com>
>
> 	* NEWS (New remote packets): Mention vCtrlC.
>
> gdb/doc/
> 2015-10-14  Pedro Alves  <palves@redhat.com>
>
> 	* gdb.texinfo (Bootstrapping): Add
> 	"interrupting remote targets" anchor.
> 	(Packets): Document vCtrlC.
>
> gdb/gdbserver/
> 2015-10-14  Pedro Alves  <palves@redhat.com>
>
> 	* server.c (handle_v_requests): Handle vCtrlC.

These entries below should be hoisted above to gdb/ChangeLog,

> 	* remote.c (PACKET_vCtrlC): New enum value.
> 	(async_remote_interrupt): Call target_interrupt instead of
> 	target_stop.
> 	(remote_interrupt_as): Remove 'ptid' parameter.
> 	(remote_interrupt_ns): New function.
> 	(remote_stop): Adjust.
> 	(remote_interrupt): If the target is in non-stop mode, try
> 	interrupting with vCtrlC.
> 	(initialize_remote): Install set remote ctrl-c packet.
> ---
>  gdb/NEWS               |  4 ++++
>  gdb/doc/gdb.texinfo    | 34 +++++++++++++++++++++++----
>  gdb/gdbserver/server.c |  7 ++++++
>  gdb/remote.c           | 64 ++++++++++++++++++++++++++++++++++++++++++++------
>  4 files changed, 98 insertions(+), 11 deletions(-)
>

>  
> +/* Non-stop version of target_interrupt.  Uses `vCtrlC' to interrupt
> +   the remote target.  It is undefined which thread of which process
> +   reports the interrupt.  */
> +

We need to document the return value of this function in comments.

> +static int
> +remote_interrupt_ns (void)
> +{
> +  struct remote_state *rs = get_remote_state ();
> +  char *p = rs->buf;
> +  char *endp = rs->buf + get_remote_packet_size ();
> +
> +  xsnprintf (p, endp - p, "vCtrlC");
> +
> +  /* In non-stop, we get an immediate OK reply.  The stop reply will
> +     come in asynchronously by notification.  */
> +  putpkt (rs->buf);
> +  getpkt (&rs->buf, &rs->buf_size, 0);
> +
> +  switch (packet_ok (rs->buf, &remote_protocol_packets[PACKET_vCtrlC]))
> +    {
> +    case PACKET_OK:
> +      break;
> +    case PACKET_UNKNOWN:
> +      return 0;
> +    case PACKET_ERROR:
> +      error (_("Interrupting target failed: %s"), rs->buf);
> +    }
> +
> +  return 1;
> +}

Patch looks good to me otherwise.

-- 
Yao (齐尧)


  reply	other threads:[~2015-10-26 11:45 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 15:28 [PATCH 00/18] Remote all-stop on top of non-stop Pedro Alves
2015-10-14 15:28 ` [PATCH 03/18] attach + target always in non-stop mode: stop all threads Pedro Alves
2015-10-26 13:22   ` Yao Qi
2015-11-23 18:15     ` Pedro Alves
2015-11-23 18:42       ` Pedro Alves
2015-11-26 16:12       ` Yao Qi
2015-11-26 16:23         ` Pedro Alves
2015-11-27  9:33           ` Yao Qi
2015-10-14 15:28 ` [PATCH 13/18] infrun: Fix TARGET_WAITKIND_NO_RESUMED handling in non-stop mode Pedro Alves
2015-10-14 15:28 ` [PATCH 01/18] Fix mi-nonstop.exp with extended-remote Pedro Alves
2015-10-14 15:28 ` [PATCH 18/18] remote: enable "maint set target-non-stop" by default Pedro Alves
2015-10-14 15:28 ` [PATCH 15/18] gdbserver:prepare_access_memory: pick another thread Pedro Alves
2015-10-14 15:28 ` [PATCH 02/18] Remote all-stop-on-top-of-non-stop Pedro Alves
2015-10-24 22:39   ` Yao Qi
2015-11-23 15:40     ` Pedro Alves
2015-11-23 18:39       ` Pedro Alves
2015-11-26 15:53         ` Yao Qi
2015-10-14 15:33 ` [PATCH 10/18] Remote thread create/exit events Pedro Alves
2015-10-14 16:35   ` Eli Zaretskii
2015-10-26 16:50   ` Yao Qi
2015-11-23 15:41     ` Pedro Alves
2015-12-01 15:12   ` Ulrich Weigand
2015-12-01 16:06     ` Pedro Alves
2015-12-01 17:10       ` Ulrich Weigand
2015-10-14 15:33 ` [PATCH 05/18] remote: stop reason and watchpoint data address per thread Pedro Alves
2015-10-14 15:36 ` [PATCH 14/18] Implement TARGET_WAITKIND_NO_RESUMED in the remote protocol Pedro Alves
2015-10-14 16:36   ` Eli Zaretskii
2015-10-19 16:21   ` Yao Qi
2015-10-19 16:48     ` Pedro Alves
2015-10-14 15:36 ` [PATCH 06/18] New vCtrlC packet, non-stop mode equivalent of \003 Pedro Alves
2015-10-26 14:11   ` Yao Qi [this message]
2015-11-30 18:25     ` Pedro Alves
2015-10-14 15:36 ` [PATCH 04/18] gdbserver crash running gdb.threads/non-ldr-exc-1.exp Pedro Alves
2015-10-26 13:54   ` Yao Qi
2015-11-24 16:34     ` Pedro Alves
2015-11-26 16:23       ` Yao Qi
2015-11-30 14:53         ` Pedro Alves
2015-10-14 15:36 ` [PATCH 12/18] testsuite: Range stepping and non-stop mode Pedro Alves
2015-10-14 15:36 ` [PATCH 17/18] gdbserver: don't exit until GDB disconnects Pedro Alves
2015-10-14 15:36 ` [PATCH 11/18] gdbserver: fix killed-outside.exp Pedro Alves
2015-10-27 12:02   ` Yao Qi
2015-11-25 15:06     ` Pedro Alves
2015-11-26 16:51       ` Yao Qi
2015-11-26 17:56         ` Pedro Alves
2015-10-14 15:37 ` [PATCH 07/18] gdbserver crash if gdb attaches too fast Pedro Alves
2015-10-14 15:37 ` [PATCH 16/18] gdbserver/linux: Always wake up event loop after resume Pedro Alves
2015-10-26 17:28   ` Yao Qi
2015-11-25 15:31     ` Pedro Alves
2015-10-14 15:37 ` [PATCH 09/18] Make dprintf-non-stop.exp cope with remote testing Pedro Alves
2015-10-14 15:38 ` [PATCH 08/18] gdbserver resume_stop handling bug Pedro Alves
2015-10-14 16:37   ` Eli Zaretskii
2015-11-25 15:12     ` Pedro Alves
2015-11-25 17:53       ` Eli Zaretskii
2015-10-15 10:46 ` [PATCH 00/18] Remote all-stop on top of non-stop Pedro Alves
2015-10-16 16:47 ` Yao Qi
2015-10-19 11:48   ` Yao Qi
2015-10-19 15:28     ` Pedro Alves
2015-10-19 15:47       ` Yao Qi
2015-10-27 13:11 ` Yao Qi
2015-11-30 19:59   ` 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=86io5t26rr.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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