FYI - I've been maintaining a similar VSCode extension <https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb>, which does it all through LLDB's Python interface.
As for testing, the protocol is JSON with HTTP-like headers for framing, so you could have a Python script emulating the VSCode side. On Wed, Feb 14, 2018 at 2:28 PM, Greg Clayton via lldb-dev < lldb-dev@lists.llvm.org> wrote: > I have a patch I will be submitting soon that adds a tool called > "lldb-vscode" that is much like "lldb-mi" where it sits on top of > LLDB.framework on Darwin and liblldb.so on all other platforms, and it > speaks the Visual Studio Code Debug adaptor language and can be used to > create a VSCode extension that does native LLDB debugging. The plug-in > works really well to debug native apps and is very responsive and quick. > > One issue I am thinking about is how to test this. Some VS Code tests out > there use Javascript + npm to run a mock VSCode IDE and send/receive > packets. I am not sure we can require people to have this on all build > bots. So I am writing to get everyone's opinion on this so I can test this > and get a patch submitted. > > Any ideas would be appreciated. > > Greg Clayton > > _______________________________________________ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev