I am glad to hear this. We will be happy to help with any issues you run into.
If you have examples for any issues you run into, it would be great to get MI text snippets that we can run through the lldb-mi program on our end, it can help us to understand and reproduce any issues you run into. > 1. -breakpoint-insert doesn't handle locations that look like absolute > paths (because of leading /) Can you send an example? > 2. Executable path has to be absolute Does MI have the notion of setting a current working directory where things can then be relative to? If so, we should definitely fix this in LLDB. Example packet of setting the working directory and then the non working executable path would be nice. Greg > On Jul 17, 2016, at 2:26 PM, Marc-Andre Laperle via lldb-dev > <lldb-dev@lists.llvm.org> wrote: > > Hi, > > I am currently working on integrating LLDB-MI in Eclipse CDT so that > it works more or less out of the box in the next CDT release due in > September (setting the lldb-mi path automatically, etc). For this > specific issue, I made it so that it simply does not send the > target-async command from Eclipse. I have worked around a few other > issues and I'll look at creating bugs in LLDB's Bugzilla and sending > patches to LLDB in the upcoming weeks. > > Here are some issues I worked around but would like to fix on the LLDB side: > 1. -breakpoint-insert doesn't handle locations that look like absolute > paths (because of leading /) > 2. Executable path has to be absolute > > This Eclipse integration is still very much in progress but in case > you are curious, the code is here: > https://github.com/MarkZ3/Eclipse-CDT-WIP/tree/lldb-mi > > Regards, > Marc-Andre > _______________________________________________ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev _______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
