summaryrefslogtreecommitdiffstats
path: root/lldb/source/Host/posix/HostProcessPosix.cpp
diff options
context:
space:
mode:
authorTodd Fiala <todd.fiala@gmail.com>2014-09-30 16:56:28 +0000
committerTodd Fiala <todd.fiala@gmail.com>2014-09-30 16:56:28 +0000
commitf8d929dc827000d109a5c619648fa239b79a18e9 (patch)
tree8e4b8a4dfc86d7dd47a9c303a3c7d43f8dfbaf1a /lldb/source/Host/posix/HostProcessPosix.cpp
parent7a770755305f19426e5748195035a26e6e673077 (diff)
downloadbcm5719-llvm-f8d929dc827000d109a5c619648fa239b79a18e9.tar.gz
bcm5719-llvm-f8d929dc827000d109a5c619648fa239b79a18e9.zip
thread state coordinator: add test to be explicit about resume behavior in presence of deferred stop notification still pending.
There is a state transition that seems potentially buggy that I am capturing and logging here, and including an explicit test to demonstrate expected behavior. See new test for detailed description. Added logging around this area since, if we hit it, we may have a usage bug, or a new state transition we really need to investigate. This is around this scenario: Thread C deferred stop notification awaiting thread A and thread B to stop. Thread A stops. Thread A requests resume. Thread B stops. Here we will explicitly signal the deferred stop notification after thread B stops even though thread A is now resumed. Copious logging happens here. llvm-svn: 218683
Diffstat (limited to 'lldb/source/Host/posix/HostProcessPosix.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud