99451b4453
Summary: Moves lldbsuite tests to lldb/test/API.
This is a largely mechanical change, moved with the following steps:
```
rm lldb/test/API/testcases
mkdir -p lldb/test/API/{test_runner/test,tools/lldb-{server,vscode}}
mv lldb/packages/Python/lldbsuite/test/test_runner/test lldb/test/API/test_runner
for d in $(find lldb/packages/Python/lldbsuite/test/* -maxdepth 0 -type d | egrep -v "make|plugins|test_runner|tools"); do mv $d lldb/test/API; done
for d in $(find lldb/packages/Python/lldbsuite/test/tools/lldb-vscode -maxdepth 1 -mindepth 1 | grep -v ".py"); do mv $d lldb/test/API/tools/lldb-vscode; done
for d in $(find lldb/packages/Python/lldbsuite/test/tools/lldb-server -maxdepth 1 -mindepth 1 | egrep -v "gdbremote_testcase.py|lldbgdbserverutils.py|socket_packet_pump.py"); do mv $d lldb/test/API/tools/lldb-server; done
```
lldb/packages/Python/lldbsuite/__init__.py and lldb/test/API/lit.cfg.py were also updated with the new directory structure.
Reviewers: labath, JDevlieghere
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D71151
33 lines
886 B
C++
33 lines
886 B
C++
#include <chrono>
|
|
#include <thread>
|
|
|
|
void
|
|
thread_function ()
|
|
{
|
|
// Set thread-specific breakpoint here.
|
|
std::this_thread::sleep_for(std::chrono::milliseconds(20));
|
|
// On Windows, a sleep_for of less than about 16 ms effectively calls
|
|
// Sleep(0). The MS standard thread implementation uses a system thread
|
|
// pool, which can deadlock on a Sleep(0), hanging not only the secondary
|
|
// thread but the entire test. I increased the delay to 20 ms to ensure
|
|
// Sleep is called with a delay greater than 0. The deadlock potential
|
|
// is described here:
|
|
// https://docs.microsoft.com/en-us/windows/win32/api/synchapi/nf-synchapi-sleep#remarks
|
|
}
|
|
|
|
int
|
|
main ()
|
|
{
|
|
// Set main breakpoint here.
|
|
|
|
#ifdef __APPLE__
|
|
pthread_setname_np("main-thread");
|
|
#endif
|
|
|
|
std::thread t(thread_function);
|
|
t.join();
|
|
|
|
thread_function();
|
|
return 0;
|
|
}
|