ivanhernandez13 added a comment. Assuming this looks good, can I get some pointers on how and where I should add a test for this?
I based this change on the one for the LLDB driver (https://reviews.llvm.org/D54692) which added lldb/trunk/lit/Driver/TestCommands.test. Should I look into adding something similar or should I be using lldb/packages/Python/lldbsuite/test/tools/lldb-vscode/lldbvscode_testcase.py and adding something in lldb/test/API/tools/lldb-vscode? This is what the output for help looks like: ~/llvm-project ❯❯❯ build/Debug/bin/lldb-vscode --help [INSERT] OVERVIEW: LLDB VSCode USAGE: lldb-vscodeoptions OPTIONS: -g Alias for --wait-for-debugger --help Prints out the usage information for the LLDB debug adapter tool. -h Alias for --help --port <port> What port to listen on. -p <value> Alias for --port --wait-for-debugger Pause the program at startup. EXAMPLES: The debug adapter can be started in two modes. Running lldb-vscode without any arguments will start communicating with the parent over stdio. Passing a port number causes lldb-vscode to start listening for connections on that port. lldb-vscode -p <port> Passing --wait-for-debugger will pause the process at startup and wait for a debugger to attach to the process. lldb-vscode -w % Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D74798/new/ https://reviews.llvm.org/D74798 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
