> On Feb 14, 2018, at 3:45 PM, Vadim Chugunov <vadi...@gmail.com> 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 since it worked so well I wanted to make a native
version of this plug-in to avoid taking over the python interpreter and get
native performance. Very nice work on that plug-in as it inspired this one! I
adopted many similar settings that you allow in the launch.json file and added
some new ones.
> As for testing, the protocol is JSON with HTTP-like headers for framing, so
> you could have a Python script emulating the VSCode side.
That is what I was planning to do. Might be nice to work together on this and
get the testing working as it could test both of our plug-ins. Would be great
to have a debug session with a simple program that sets a breakpoint by name,
by file and line and exception and run, hit the breakpoints, view variables,
> On Wed, Feb 14, 2018 at 2:28 PM, Greg Clayton via lldb-dev
> <firstname.lastname@example.org <mailto:email@example.com>> 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
> 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
> Any ideas would be appreciated.
> Greg Clayton
> lldb-dev mailing list
> firstname.lastname@example.org <mailto:email@example.com>
lldb-dev mailing list