Re: [lldb-dev] How to test lldb-vscode?

Mocking the VS side (in python or C++) sounds like the way to go. I don't know much smartness is in this code (as in, something other than "take this json, translate it to an appropriate SB call and serialize the results back"), but if there is some non-trivial logic in there (perhaps the code

Re: [lldb-dev] How to test lldb-vscode?

The SB API's were designed to be binary stable API's when used either from C++ or Python (the latter are just a SWIG-ified version of the former.) So just like the Python wrapper, with the exception that you might call an API that some older version of liblldb doesn't provide, Greg's adaptor

Re: [lldb-dev] How to test lldb-vscode?

My tests are here . I probably wouldn't move all that to Python for my extension, but feel free to draw ideas on things to test from it. What's going to be your deployment story? The nice thing about

Re: [lldb-dev] How to test lldb-vscode?

> On Feb 14, 2018, at 3:45 PM, Vadim Chugunov wrote: > > FYI - I've been maintaining a similar VSCode extension > , > which does it all through LLDB's Python interface. Indeed, I saw you plug-in and

Re: [lldb-dev] How to test lldb-vscode?

FYI - I've been maintaining a similar VSCode extension , 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

[lldb-dev] How to test lldb-vscode?

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