Note that since you are using MI as the interface between your debugger GUI and the debugging backend (gdb) you can try using the lldb-mi layer and test performance between the GDB MI and the LLDB MI. Then you can rename your debugger to be UltraMI to keep your debugger agnostic the the backend debugger. :-)
I noticed in the youtube video that it took 40 seconds to set a breakpoint at lldb's main function and to run to the breakpoint and hit it. If you try LLDB MI, I am guessing it will be faster than 40 seconds. Greg Clayton > On Jul 7, 2015, at 12:46 PM, Xu,Chiheng <chiheng...@gmail.com> wrote: > > On Wed, Jul 8, 2015 at 3:18 AM, Sergio Durigan Junior > <sergi...@redhat.com> wrote: >> >> I tried to find the source code of this package, but I could not find >> it. Do you have a URL or something you can provide? >> > Sorry, source code of UltraGDB is not available now. The source code > is actually a trimmed down, supercharged, and re-branded Eclipse CDT. > All of our technology is built on open source, and for open source. It > maybe weird for us not to provide the source code. But we are just > founded, we have no idea how to continue developing this product. In > other word, we have no business model yet. At present, we just want > to know whether or not our product is useful, if so, then we think it > is meaningful to work on it. > > This product is actually a part of much bigger and more ambitious plan > that can't be disclosed right now. In the future, we may decide to > provide the source code of UltraGDB. > > Any comment or suggestion on the UltraGDB product, or "development > model", or "business model" is welcomed. > > > -- > Xu,Chiheng(εΎζζ) > > _______________________________________________ > lldb-dev mailing list > lldb-...@cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
