Re: [lldb-dev] [GSoC] Re-implement lldb-mi on top of the LLDB public API

There are lots of them, so I don't think I can list them all. But if you are interested in some command you need to do a few simple steps: 1) go to GDB/MI specification and find the command you are interested in; 2) go to lldb-mi and try t

Re: [lldb-dev] [GSoC] Re-implement lldb-mi on top of the LLDB public API

Can you please list the missing MI commands? This would be very valuable to both future contributors and also to the users of the LLDB MI. Thanks! On Mon, Aug 13, 2018 at 11:28 AM, Александр Поляков wrote: > Thank you, Leonard, > I'm going to keep contributing to LLVM, so I think this is not the

Re: [lldb-dev] [GSoC] Re-implement lldb-mi on top of the LLDB public API

Thank you, Leonard, I'm going to keep contributing to LLVM, so I think this is not the end! On Mon, Aug 13, 2018 at 8:15 PM Leonard Mosescu wrote: > Nice to see great progress in this area! > > On Sun, Aug 12, 2018 at 2:49 PM, Александр Поляков via lldb-dev < > lldb-dev@lists.llvm.org> wrote: >

Re: [lldb-dev] [GSoC] Re-implement lldb-mi on top of the LLDB public API

Nice to see great progress in this area! On Sun, Aug 12, 2018 at 2:49 PM, Александр Поляков via lldb-dev < lldb-dev@lists.llvm.org> wrote: > Hi LLVM folks, > > During this summer I was working on re-implementing of lldb-mi to > correctly use LLDB public API. You are welcome to read my final repor

[lldb-dev] [GSoC] Re-implement lldb-mi on top of the LLDB public API

Hi LLVM folks, During this summer I was working on re-implementing of lldb-mi to correctly use LLDB public API. You are welcome to read my final report where I describe the contribution and challenges I faced with. Link to final report: https://apolyakov.github.io/GSoC-2018/ -- Alexander ___