llvm-project/lldb/test/Shell/Process
Raphael Isemann d4b08ccb87 [lldb] Replace TestAbortExitCode with a debugserver specific test
When I added TestAbortExitCode I actually planned this to be a generic test for the
exit code functionality on POSIX systems. However due to all the different test setups we
can have I don't think this worked out. Right now the test had to be made so permissive
that it pretty much can't fail.

Just to summarize, we would need to support the following situations:
1. ToT debugserver (on macOS)
2. lldb-server (on other platforms)
3. Any old debugserver version when using the system debugserver (on macOS)

This patch is removing TestAbortExitCode and adds a ToT debugserver specific test
that checks the patch that motivated the whole exit code testing. There is already
an exit-code test for lldb-server from what I can see and 3) is pretty much untestable
as we don't know anything about the system debugserver.

Reviewed By: kastiglione

Differential Revision: https://reviews.llvm.org/D89305
2020-11-12 17:33:21 +01:00
..
Inputs [lldb] Replace TestAbortExitCode with a debugserver specific test 2020-11-12 17:33:21 +01:00
Windows [test] Replace `yaml2obj >` with `yaml2obj -o` and remove unneeded input redirection 2020-08-20 15:01:09 -07:00
Optimization.test Restrict test for DW_AT_APPLE_optimized to Darwin 2020-05-22 15:52:00 -07:00
TestEnvironment.test [lldb/Test] Use lit's capabilities to skip lldb-repro tests. 2020-01-22 13:24:12 -08:00
UnsupportedLanguage.test Print a warning when stopped in a frame LLDB has no plugin for. 2020-05-22 15:37:36 -07:00