[lldb-dev] LLDB Machine Interface Frontend

Fri May 16 11:55:36 PDT 2014

On Fri, May 16, 2014 at 8:23 PM, Deepak Panickal <deepak at codeplay.com>wrote:

>  Hi Eran,
>
> I tried it here with a Debug build and a MinSizeRel build, but no crashes.
>
> Did you try to launch it from an IDE or simply ran it?
>
I tried it from the command line

FYI:
I am using Windows 7 (64), Visual Studio 2013 (express edition)
Can you upload your lldb-mi.exe / liblldb.dll somewhere so I could try it
here and see if its a problem with my build?

>  Could you please try a debug build?
>
Will do

> We'll look into it more to see if we can find something.
>
> Thanks,
> Deepak
>
>
> On 16/05/2014 17:04, Eran Ifrah wrote:
>
>  Hi Deepak,
>
>  I have just updated and rebuilt the tree on Windows
>  Starting lldb-mi.exe -> instantly crashes
>  for comparison, starting lldb.exe it starts normally without any crash
>
>  I built it using VS2013, I selected the 'MinSizeRel' build configuration
>  Unfortunately, running it under VS, gives a useless backtrace (only
> addresses)
>
>  I could try and build it with debug info, but it just takes too much
> time :D
>
>  Eran
>
>
>
>
> On Fri, May 16, 2014 at 6:50 PM, <jingham at apple.com> wrote:
>
>> Excellent!  Again, thanks for working on this.
>>
>> Jim
>>
>> On May 16, 2014, at 4:15 AM, Deepak Panickal <deepak at codeplay.com> wrote:
>>
>> > 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, jingham at apple.com 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 <deepak at codeplay.com>
>> 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: lldb-dev-bounces at cs.uiuc.edu [mailto:
>> lldb-dev-bounces at cs.uiuc.edu]
>> >>>>> On Behalf Of Deepak Panickal
>> >>>>> Sent: 15 May 2014 12:14
>> >>>>> To: lldb-dev at cs.uiuc.edu
>> >>>>> 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
>> >>>>> lldb-dev at cs.uiuc.edu
>> >>>>> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>> >>>
>> <lldb-mi-driver.patch.bz2>_______________________________________________
>> >>> lldb-dev mailing list
>> >>> lldb-dev at cs.uiuc.edu
>> >>> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>> >
>>
>> _______________________________________________
>> lldb-dev mailing list
>> lldb-dev at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>>
>
>
>
> --
> Eran Ifrah
> Author of codelite, a cross platform open source C/C++ IDE:
> http://www.codelite.org
>  wxCrafter, a wxWidgets RAD: http://wxcrafter.codelite.org
>
>
>

-- 
Eran Ifrah
Author of codelite, a cross platform open source C/C++ IDE:
http://www.codelite.org
wxCrafter, a wxWidgets RAD: http://wxcrafter.codelite.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20140516/c035fed8/attachment.html>