Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 14/18] Implement TARGET_WAITKIND_NO_RESUMED in the remote protocol
Date: Wed, 14 Oct 2015 16:36:00 -0000	[thread overview]
Message-ID: <83bnc1xv8s.fsf@gnu.org> (raw)
In-Reply-To: <1444836486-25679-15-git-send-email-palves@redhat.com>

> From: Pedro Alves <palves@redhat.com>
> Date: Wed, 14 Oct 2015 16:28:02 +0100
> 
> gdb/ChangeLog:
> 2015-10-14  Pedro Alves  <palves@redhat.com>
> 
> 	PR 14618
> 	* NEWS (New remote packets): Mention the N stop reply.
> 	* remote.c (remote_protocol_features): Add "no-resumed" entry.
> 	(remote_query_supported): Report no-resumed+ support.
> 	(remote_parse_stop_reply): Handle 'N'.
> 	(process_stop_reply): Handle TARGET_WAITKIND_NO_RESUMED.
> 	(remote_wait_as): Handle 'N' / TARGET_WAITKIND_NO_RESUMED.
> 	(_initialize_remote): Register "set/show remote
> 	no-resumed-stop-reply" commands.
> 
> gdb/doc/ChangeLog:
> 2015-10-14  Pedro Alves  <palves@redhat.com>
> 
> 	PR 14618
> 	* gdb.texinfo (Stop Reply Packets): Document the N stop reply.
> 	(Remote Configuration): Add the "set/show remote
> 	no-resumed-stop-reply" to the available settings table.
> 	(General Query Packets): Document the "no-resumed" qSupported
> 	feature.
> 
> gdb/gdbserver/ChangeLog:
> 2015-10-14  Pedro Alves  <palves@redhat.com>
> 
> 	PR 14618
> 	* linux-low.c (linux_wait_1): If the last resumed thread is gone,
> 	report TARGET_WAITKIND_NO_RESUMED.
> 	* remote-utils.c (prepare_resume_reply): Handle
> 	TARGET_WAITKIND_NO_RESUMED.
> 	* server.c (report_no_resumed): New global.
> 	(handle_query) <qSupported>: Handle "no-resumed+".  Report
> 	"no-resumed+" support.
> 	(resume): When the target reports TARGET_WAITKIND_NO_RESUMED, only
> 	return error if the client doesn't support no-resumed events.
> 	(push_stop_notification): New function.
> 	(handle_target_event): Use it.  Report TARGET_WAITKIND_NO_RESUMED
> 	events if the client supports them.

OK for the documentation parts.

Thanks.


  reply	other threads:[~2015-10-14 16:36 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 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: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:33 ` [PATCH 05/18] remote: stop reason and watchpoint data address per thread Pedro Alves
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: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 06/18] New vCtrlC packet, non-stop mode equivalent of \003 Pedro Alves
2015-10-26 14:11   ` Yao Qi
2015-11-30 18:25     ` 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:36 ` [PATCH 12/18] testsuite: Range stepping and non-stop mode 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 [this message]
2015-10-19 16:21   ` Yao Qi
2015-10-19 16:48     ` 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: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: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=83bnc1xv8s.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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