[lldb-dev] Graphical lldb

[Jason Molenda]

You might want to look at test/api/multiple-debuggers/multi-process-driver.cpp which is an example C++ driver program which creates an lldb debug session (50 of them, actually), inserts breakpoints, runs to the breakpoints, backtraces and continues as a simple example in C++.

(the test itself is trying to hit race conditions with multiple debuggers running at the same time on separate threads.)


J

> On Nov 10, 2014, at 1:30 PM, jingham at apple.com wrote:
> 
> The SB API's are a C++ interface to lldb (that's how Xcode uses them, for example.)  Those C++ API's are translated into
> a Python interface (using the SWIG tool) for scripting purposes.  But you should feel free to use the C++ version if you like C++.
> 
> I think Greg just suggested Python because it's an easy way to play around and figure out how they work.
> 
> Jim
> 
> 
>> On Nov 10, 2014, at 1:03 PM, Jose H <jose.francisco.hevia at gmail.com> wrote:
>> 
>> @jingham: Oh, simple. I just wanted a better way to handle the errors
>> and output of lldb that just having a text file stream that I have to
>> parse to understand, because I want the GUI to understand some things
>> like an error happened or not and I just can't stand parsing stuff.
>> 
>> Anyway, I have read a lot of code meanwhile and I understand lldb much
>> better now.
>> 
>> About the SB API's, it forces me to use python, but I am using C++ so
>> I prefer to use the c++ equivalent if possible. Not that it looks too
>> hard as the SP APIs seem direct mappings of the c++ objects.
>> 
>> I am using C++ because I already have lots of graphic code on
>> c/c++(years of work) that I want to use in this project.
>> _______________________________________________
>> 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