Thanks Jim, have just committed it. Yeah, it works with the GDB/MI
interface.
There's no GPL code, it's all written from scratch.
Not all MI commands have been implemented yet, however it should be
enough to set breakpoints, view locals.
We're working on adding more commands for viewing/modifying registers,
memory etc.
It'll be great if more people from the community can use and test it
with other GUIs!
Thanks,
Deepak
On 15/05/2014 18:57, [email protected] wrote:
First off, thanks for doing this, that is great! If this also works with the
gdb-mi mode, you will make our emacs friends happy as well.
If this is just an independent tool that doesn't touch the core lldb sources
(and doesn't use anything directly from the gdb MI implementation, since we
don't want to mix GPL'ed code in with lldb), I see no reason not to just check
it in now, and then iterate on it in situ. That is much easier than handing
around patch files, and since there's no chance it will interfere with anybody
working on parts of lldb that existed before the patch, can't do any harm. I
spoke to GregC and he agrees this is a reasonable course.
Again, thanks for working on this.
Jim
On May 15, 2014, at 10:17 AM, Deepak Panickal <[email protected]> wrote:
Hi Abid,
Thank you, I have attached the zipped patch.
You might have to the change the triple in tools/lldb-mi/MICmnConfig.h for your
target.
Please let me know if you have any comments/suggestions.
Thanks,
Deepak
On 15/05/2014 17:10, Abid, Hafiz wrote:
Hi Deepak,
I can help review/test it when you post the patch.
Thanks,
Abid
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Deepak Panickal
Sent: 15 May 2014 12:14
To: [email protected]
Subject: [lldb-dev] LLDB Machine Interface Frontend
Hi,
We have an MI (Machine Interface) frontend to LLDB which works out of the
box with Eclipse, and likely will work with other GUI's based on the GDB/MI
interface. It's been tested on Linux and Windows.
It's ready to upstream and has been developed as an independent tool
residing in the LLDB tools folder. It's based on the LLDB public API without
any changes to LLDB internals.
The patch is quite large as there are many new files.
How should we go about upstreaming? Should I create a diff review as
usual?
Thanks,
Deepak
_______________________________________________
lldb-dev mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
<lldb-mi-driver.patch.bz2>_______________________________________________
lldb-dev mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
_______________________________________________
lldb-dev mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
