forked from OSchip/llvm-project
9cf21da776
The TestGdbRemote_vContThreads.py were introduced to test NetBSD process plugin's capability of sending per-thread and per-process signals. However, at some point the tests started failing. From retrospective, it is possible that they were relying on some bug in the plugin's original signal handling. Fix the tests not to expect the process to terminate after receiving the signals. Instead, scan for output indicating that the signals were received and match thread IDs in it. Enable 'signal to all threads' test everywhere as it works fine on Linux. Add a new test for vCont packet without specific thread IDs. Introduce a helper function to cover the common part of tests. While this does not fix all the problems on NetBSD, it enables a subset of the tests on other systems. I am planning to add more tests to the group while implementing multiprocess extension for vCont. Differential Revision: https://reviews.llvm.org/D98749 |
||
|---|---|---|
| .. | ||
| bindings | ||
| cmake | ||
| docs | ||
| examples | ||
| include/lldb | ||
| packages/Python | ||
| resources | ||
| scripts | ||
| source | ||
| test | ||
| third_party/Python/module | ||
| tools | ||
| unittests | ||
| utils | ||
| .clang-format | ||
| .clang-tidy | ||
| .gitignore | ||
| CMakeLists.txt | ||
| CODE_OWNERS.txt | ||
| LICENSE.TXT | ||
| use_lldb_suite_root.py | ||