diff options
| author | Pedro Alves <pedro@palves.net> | 2021-12-03 22:10:05 +0000 |
|---|---|---|
| committer | Pedro Alves <pedro@palves.net> | 2023-11-13 14:16:10 +0000 |
| commit | faf44a3105670f74095f6552e3cd7b107fbbb6b3 (patch) | |
| tree | 792aeddde2ee1d2183ed9e7ba989e9be5a90de9d /gdb/testsuite/gdb.python/py-section-script.py | |
| parent | 393a6b5947d037a55ce1b57474e1ffb3074f544e (diff) | |
| download | binutils-faf44a3105670f74095f6552e3cd7b107fbbb6b3.zip binutils-faf44a3105670f74095f6552e3cd7b107fbbb6b3.tar.gz binutils-faf44a3105670f74095f6552e3cd7b107fbbb6b3.tar.bz2 | |
gdbserver: Hide and don't detach pending clone children
This commit extends the logic added by these two commits from a while
ago:
#1 7b961964f866 (gdbserver: hide fork child threads from GDB),
#2 df5ad102009c (gdb, gdbserver: detach fork child when detaching from fork parent)
... to handle thread clone events, which are very similar to (v)fork
events.
For #1, we want to hide clone children as well, so just update the
comments.
For #2, unlike (v)fork children, pending clone children aren't full
processes, they're just threads, so don't detach them in
handle_detach. linux-low.cc will take care of detaching them along
with all other threads of the process, there's nothing special that
needs to be done.
Reviewed-By: Andrew Burgess <aburgess@redhat.com>
Change-Id: I7f5901d07efda576a2522d03e183994e071b8ffc
Diffstat (limited to 'gdb/testsuite/gdb.python/py-section-script.py')
0 files changed, 0 insertions, 0 deletions