It is a different protocol. The LLDB MI plugin didn't work very well as was 
quite flaky when I tested it a while back. Then I grabbed the CodeLLDB plugin 
by Vadim Chugunov and it worked very well. When I looked more closely at this 
plugin, it was using a javascript/typescript plug-in to launch a LLDB instance 
and then ran a python script that received all of the javascript packets from 
the javascript/typescript based plug-in and ran the debug session. It worked 
very well and was rock solid stable. So I then created this plug-in for Nuclide 
for use at Facebook as they switched all of the debugging plug-in over to use 
the VSCode debug adaptor protocols. It works event better than the CodeLLDB 
plugin with Visual Studio Code and it also doesn't stop you from using the 
python interpreter. The issue I had with the CodeLLDB is that is uses the 
python interpreter to run the debug session thus it isn't available to you as a 
LLDB user.

So long story short: our IDE at Facebook uses the VSCode protocol, MI is clunky 
and doesn't work that well and was flaky, so this tool was created. This also 
provides a really nice way to do remote debugging where the lldb-vscode is run 
remotely on other systems. This removes the need for copying files from a 
remote host up onto the system that is doing the debugging.

Greg

> On Aug 8, 2018, at 8:30 AM, Zachary Turner <ztur...@google.com> wrote:
> 
> How does this differ from VS Code's builtin LLDB MI support?
> 
> On Wed, Aug 8, 2018 at 8:15 AM Pavel Labath via Phabricator 
> <revi...@reviews.llvm.org <mailto:revi...@reviews.llvm.org>> wrote:
> labath added a comment.
> 
> To end things on a positive note: I think the test coverage is pretty good 
> (I'm sure somebody will suggest switching to lit), and I think a VS code 
> plugin would be a great addition to lldb.
> 
> 
> https://reviews.llvm.org/D50365 <https://reviews.llvm.org/D50365>
> 
> 
> 

_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to