[PATCH 03/10] remote+gdbserver: stepped-thread-exited feature

[Eli Zaretskii]

> From: Pedro Alves <pedro@palves.net>
> Date: Fri,  2 Jul 2021 14:01:47 +0100
> gdb/ChangeLog:
> yyyy-mm-dd  Pedro Alves  <pedro@palves.net>
> 	    Simon Marchi  <simon.marchi@efficios.com>
> 
> 	PR gdb/27338
> 	* NEWS: Mention stepped-thread-exited feature in qSupported.
> 	* remote.c (PACKET_stepped_thread_exited): New.
> 	(remote_protocol_features): Add "stepped-thread-exited" entry.
> 	(remote_target::remote_query_supported): Report
> 	stepped-thread-exited+.
> 	(remote_target::wait_as): Handle 'w' (aka thread exit) stop reply.
> 	(_initialize_remote): Register "set/show remote
> 	stepped-thread-exited-stop-reply".
> 
> gdbserver/ChangeLog:
> yyyy-mm-dd  Pedro Alves  <pedro@palves.net>
> 
> 	PR gdb/27338
> 	* server.cc (handle_query): Handle and report
> 	stepped-thread-exited+.
> 	(resume): Handle TARGET_WAITKIND_THREAD_EXITED in all-stop mode.
> 
> gdb/doc/ChangeLog:
> yyyy-mm-dd  Pedro Alves  <pedro@palves.net>
> 
> 	PR gdb/27338
> 	* gdb.texinfo (Remote Configuration): Document
> 	stepped-thread-exited-stop-reply.
> 	(Stop Reply Packets) <w stop reply>: Mention
> 	stepped-threads-exited feature.
> 	(General Query Packets): Document stepped-thread-exited.
> 

Thanks.

In the documentation parts, I'm confused by the terms "thread exited
event" and "stepping threads".  They are not explained anywhere,
AFAICS.  Could we explain them, or perhaps use some more clear
terminology?  E.g., at one place you use "single-stepped thread that
exit", which is clear (assuming that's what you mean by "stepping
threads").