Александр Поляков via llvm-dev
2018-Aug-12 21:49 UTC
[llvm-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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180813/4fa5f8be/attachment.html>
Leonard Mosescu via llvm-dev
2018-Aug-13 17:15 UTC
[llvm-dev] [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 at 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 report > where I describe the contribution and challenges I faced with. > Link to final report: https://apolyakov.github.io/GSoC-2018/ > > -- > Alexander > > _______________________________________________ > lldb-dev mailing list > lldb-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180813/847f1e03/attachment-0001.html>
Александр Поляков via llvm-dev
2018-Aug-13 18:28 UTC
[llvm-dev] [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 <mosescu at google.com> wrote:> Nice to see great progress in this area! > > On Sun, Aug 12, 2018 at 2:49 PM, Александр Поляков via lldb-dev < > lldb-dev at 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 report >> where I describe the contribution and challenges I faced with. >> Link to final report: https://apolyakov.github.io/GSoC-2018/ >> >> -- >> Alexander >> >> _______________________________________________ >> lldb-dev mailing list >> lldb-dev at lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >> >> >-- Alexander -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180813/dfc7fb3b/attachment.html>
Seemingly Similar Threads
- [lldb-dev] [GSoC] Re-implement lldb-mi on top of the LLDB public API
- [lldb-dev] [GSoC] Re-implement lldb-mi on top of the LLDB public API
- Re: deadlock on connection loosing
- Re: libvirt hang on domain attemp to create domain
- Re: libvirt hang on domain attemp to create domain