aboutsummaryrefslogtreecommitdiff
path: root/llvm/tools/llvm-ml/Disassembler.cpp
diff options
context:
space:
mode:
authorJim Ingham <jingham@apple.com>2020-02-13 15:48:38 -0800
committerJim Ingham <jingham@apple.com>2020-02-13 15:48:38 -0800
commit4570f2c7cf35388d8b3ab9cc5cdcad4971e31cf2 (patch)
tree00e9d99cca1c0f096eae4e60b1e42c3711d6bab3 /llvm/tools/llvm-ml/Disassembler.cpp
parentb21c7999520a83aedcffb7e3f9399bb3603cfcca (diff)
downloadllvm-4570f2c7cf35388d8b3ab9cc5cdcad4971e31cf2.zip
llvm-4570f2c7cf35388d8b3ab9cc5cdcad4971e31cf2.tar.gz
llvm-4570f2c7cf35388d8b3ab9cc5cdcad4971e31cf2.tar.bz2
Add a test for debugserver handling threads suspended from within a program.
Mach allows you to suspend and resume other threads within a program, so debugserver has to be careful not to interfere with this when it goes to supend and resume threads while stepping over breakpoints and calling functions. Even trickier, if you call a function on a suspended thread, it has to resume the thread to get the expression to run, and then suspend it properly when done. This all works already, but there wasn't a test for it. Adding that here. This same test could be written for a unix that supports pthread_{suspend,resume}_np, but macOS doesn't support these calls, only the mach version. It doesn't look like a lot of Linux'es support this (AIX does apparently...) And IIUC Windows allows you to suspend and resume other threads, but the code for that would look pretty different than this main.c. So for simplicity's sake I wrote this test for Darwin-only.
Diffstat (limited to 'llvm/tools/llvm-ml/Disassembler.cpp')
0 files changed, 0 insertions, 0 deletions