diff options
| author | Andrew Burgess <aburgess@redhat.com> | 2023-10-10 10:00:10 +0100 |
|---|---|---|
| committer | Andrew Burgess <aburgess@redhat.com> | 2023-11-08 13:28:09 +0000 |
| commit | 3c09fd57e6f825672964581e152bd50b507e5630 (patch) | |
| tree | 263854000cd04baaeae8427a2e55758adaa669cd /gdb/ppc-linux-tdep.c | |
| parent | 75b2eb97a49bf3b539d7e016b2d9a2339170a680 (diff) | |
| download | binutils-3c09fd57e6f825672964581e152bd50b507e5630.zip binutils-3c09fd57e6f825672964581e152bd50b507e5630.tar.gz binutils-3c09fd57e6f825672964581e152bd50b507e5630.tar.bz2 | |
gdb: call update_thread_list after completing an inferior call
I noticed that if GDB is using a remote or extended-remote target,
then, if an inferior call caused a new thread to appear, or for an
existing thread to exit, then these events are not reported to the
user.
The problem is that for these targets GDB relies on a call to
update_thread_list to learn about changes to the inferior's thread
list.
If GDB doesn't pass through the normal stop code then GDB will not
call update_thread_list, and so will not report changes in the thread
list.
This commit adds an additional update_thread_list call, after which
thread events are correctly reported.
Diffstat (limited to 'gdb/ppc-linux-tdep.c')
0 files changed, 0 insertions, 0 deletions