From: Greg Clayton <gclayton@apple.com>
To: "Xu,Chiheng" <chiheng.xu@gmail.com>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>,
lldb-dev@cs.uiuc.edu, GCC <gcc@gcc.gnu.org>,
gdb@sourceware.org
Subject: Re: [lldb-dev] [AD] UltraGDB, an alternative tool to debug GCC, GDB, LLDB, etc. on Windows and Linux
Date: Tue, 07 Jul 2015 23:41:00 -0000 [thread overview]
Message-ID: <1FB41DC8-9A4D-4F7C-AB7D-174A0648C984@apple.com> (raw)
In-Reply-To: <CAPOVtOs9xRMyJ_Q=byf0DcSUhB3TV_m8is9uH0oAzv_WeiBMqw@mail.gmail.com>
Note that since you are using MI as the interface between your debugger \x10GUI 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.xu@gmail.com> wrote:
>
> On Wed, Jul 8, 2015 at 3:18 AM, Sergio Durigan Junior
> <sergiodj@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-dev@cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
next prev parent reply other threads:[~2015-07-07 23:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 8:35 Xu,Chiheng
2015-07-07 19:18 ` Sergio Durigan Junior
2015-07-07 19:46 ` Xu,Chiheng
2015-07-07 20:56 ` Sergio Durigan Junior
2015-07-07 23:41 ` Greg Clayton [this message]
2015-07-08 14:48 ` Xu,Chiheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1FB41DC8-9A4D-4F7C-AB7D-174A0648C984@apple.com \
--to=gclayton@apple.com \
--cc=chiheng.xu@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=lldb-dev@cs.uiuc.edu \
--cc=sergiodj@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox