[Lldb-commits] [PATCH] D62887: Update the thread list before setting stop reasons with an OS plugin

[Jim Ingham via Phabricator via lldb-commits]

jingham updated this revision to Diff 206980.
jingham added a comment.

Addresses Greg's question about what happens when we load a new OS plugin.  Indeed we should limit the work we do only to the case where we didn't have an OS plugin, then tried to load one and succeeded.  Only then do we need to clear and update the thread list.


Repository:
  rLLDB LLDB

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D62887/new/

https://reviews.llvm.org/D62887

Files:
  packages/Python/lldbsuite/test/functionalities/gdb_remote_client/TestRecognizeBreakpoint.py
  packages/Python/lldbsuite/test/functionalities/gdb_remote_client/gdbclientutils.py
  packages/Python/lldbsuite/test/functionalities/gdb_remote_client/operating_system_2.py
  source/Host/common/Editline.cpp
  source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
  source/Target/Process.cpp

-------------- next part --------------
A non-text attachment was scrubbed...
Name: D62887.206980.patch
Type: text/x-patch
Size: 11635 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20190628/04ce52ca/attachment.bin>