diff options
| author | Pedro Alves <pedro@palves.net> | 2021-11-23 20:35:12 +0000 |
|---|---|---|
| committer | Pedro Alves <pedro@palves.net> | 2023-11-13 14:16:09 +0000 |
| commit | 53de5394f7bf11995b1d9cb6885a8490b2ebc9da (patch) | |
| tree | 4b55592d4c2bdd5787e4d251c7a7b6d9ea679cc6 /gdb/infrun.c | |
| parent | 0d36baa9af0d9929c96b89a184a469c432c68b0d (diff) | |
| download | gdb-53de5394f7bf11995b1d9cb6885a8490b2ebc9da.zip gdb-53de5394f7bf11995b1d9cb6885a8490b2ebc9da.tar.gz gdb-53de5394f7bf11995b1d9cb6885a8490b2ebc9da.tar.bz2 | |
Support clone events in the remote protocol
The previous patch taught GDB about a new
TARGET_WAITKIND_THREAD_CLONED event kind, and made the Linux target
report clone events.
A following patch will teach Linux GDBserver to do the same thing.
But before we get there, we need to teach the remote protocol about
TARGET_WAITKIND_THREAD_CLONED. That's what this patch does. Clone is
very similar to vfork and fork, and the new stop reply is likewise
handled similarly. The stub reports "T05clone:...".
GDBserver core is taught to handle TARGET_WAITKIND_THREAD_CLONED and
forward it to GDB in this patch, but no backend actually emits it yet.
That will be done in a following patch.
Documentation for this new remote protocol feature is included in a
documentation patch later in the series.
Reviewed-By: Andrew Burgess <aburgess@redhat.com>
Change-Id: If271f20320d864f074d8ac0d531cc1a323da847f
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=19675
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=27830
Diffstat (limited to 'gdb/infrun.c')
0 files changed, 0 insertions, 0 deletions