From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 10/18] Remote thread create/exit events
Date: Wed, 14 Oct 2015 16:35:00 -0000 [thread overview]
Message-ID: <83d1whxvbi.fsf@gnu.org> (raw)
In-Reply-To: <1444836486-25679-11-git-send-email-palves@redhat.com>
> From: Pedro Alves <palves@redhat.com>
> Date: Wed, 14 Oct 2015 16:27:58 +0100
>
> gdb/doc/ChangeLog:
> 2015-10-14 Pedro Alves <palves@redhat.com>
>
> * gdb.texinfo (Remote Configuration): List "set/show remote
> thread-events" command in configuration table.
> (Stop Reply Packets): Document "T05 create" stop
> reason and 'w' stop reply.
> (General Query Packets): Document QThreadEvents packet. Document
> QThreadEvents qSupported feature.
>
> gdb/gdbserver/ChangeLog:
> 2015-10-14 Pedro Alves <palves@redhat.com>
>
> * linux-low.c (handle_extended_wait): Assert that the LWP's
> waitstatus is TARGET_WAITKIND_IGNORE. If GDB wants to hear about
> thread create events, leave the new child's status pending.
> (linux_low_filter_event): If GDB wants to hear about thread exit
> events, leave the LWP marked dead and don't delete it.
> (linux_wait_for_event_filtered): Don't check for thread exit.
> (filter_exit_event): New function.
> (linux_wait_1): Use it, when returning an exit event.
> (linux_resume_one_lwp_throw): Assert that the LWP's
> waitstatus is TARGET_WAITKIND_IGNORE.
> * remote-utils.c (prepare_resume_reply): Handle
> TARGET_WAITKIND_THREAD_CREATED and TARGET_WAITKIND_THREAD_EXITED.
> * server.c (report_thread_events): New global.
> (handle_general_set): Handle QThreadEvents.
> * server.h (report_thread_events): Declare.
>
> gdb/ChangeLog:
> 2015-10-14 Pedro Alves <palves@redhat.com>
>
> * NEWS (New commands): Mention "set/show remote thread-events"
> commands.
> (New remote packets): Mention thread created/exited stop reasons
> and QThreadEvents packet.
> * infrun.c (disable_thread_events): New function.
> (stop_all_threads): Disable/enable thread create/exit events.
> Handle TARGET_WAITKIND_THREAD_EXITED.
> (handle_inferior_event_1): Handle TARGET_WAITKIND_THREAD_CREATED
> and TARGET_WAITKIND_THREAD_EXITED.
> * remote.c (remove_child_of_pending_fork): Also remove threads of
> threads that have TARGET_WAITKIND_THREAD_EXITED events.
> (remote_parse_stop_reply): Handle "create" magic register. Handle
> 'w' stop reply.
> (initialize_remote): Install remote_thread_events as
> to_thread_events target hook.
> (remote_thread_events): New function.
> * target-delegates.c: Regenerate.
> * target.c (target_thread_events): New function.
> * target.h (struct target_ops) <to_thread_events>: New field.
> (target_thread_events): Declare.
> * target/waitstatus.c (target_waitstatus_to_string): Handle
> TARGET_WAITKIND_THREAD_CREATED and TARGET_WAITKIND_THREAD_EXITED.
> * target/waitstatus.h (enum target_waitkind)
> <TARGET_WAITKIND_THREAD_CREATED, TARGET_WAITKIND_THREAD_EXITED):
> New values.
OK for the documentation parts, thanks.
next prev parent reply other threads:[~2015-10-14 16:35 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 18/18] remote: enable "maint set target-non-stop" by default 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 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 15/18] gdbserver:prepare_access_memory: pick another 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 [this message]
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
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=83d1whxvbi.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