aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Transforms/Utils/Debugify.cpp
diff options
context:
space:
mode:
authorMichał Górny <mgorny@moritz.systems>2021-03-17 00:04:06 +0100
committerMichał Górny <mgorny@moritz.systems>2021-03-17 17:30:28 +0100
commit9cf21da776b5e71da46826ba941147495285f106 (patch)
treea253f09184e253d45d2b94fade5b78451c29278b /llvm/lib/Transforms/Utils/Debugify.cpp
parent1236dbc2fadfc0466a0a62eb147cdd3565c4898d (diff)
downloadllvm-9cf21da776b5e71da46826ba941147495285f106.zip
llvm-9cf21da776b5e71da46826ba941147495285f106.tar.gz
llvm-9cf21da776b5e71da46826ba941147495285f106.tar.bz2
[lldb] [test] Fix TestGdbRemote_vContThreads.py logic
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
Diffstat (limited to 'llvm/lib/Transforms/Utils/Debugify.cpp')
0 files changed, 0 insertions, 0 deletions