Hi Lists,
I have to implement a graphical interface to open the Dump of Macos with
LLDB.
I know how to do this using the command line, but this and less productive,
I found that LLDB-MI little make me an interface to do this need but I did
not find an example of LLDB-MI in C ++ and How to build LLD
lldb-mi uses the gdb/mi interface, which is defined here:
https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI.html . The lldb-mi
implementation is slightly different in some ways, but nothing that should
affect what you want to do.
Looking at the code (in /tools/lldb-mi/MICmdCmdFile.cpp) fo
Hello all,
we are trying to convert some of the lldb tests to lit (for these
specific tests we are using the googletest format). One of our
requirements is that we are able to run these tests remotely, so that
we are able to verify that we can debug e.g. android arm binaries even
though our develo
You might want to look at the compiler-rt tests, which have support for
remote runs. Search for the '%run' substitution. It's probably not directly
applicable to gtest tests, though.
On Fri, May 26, 2017 at 8:17 AM, Pavel Labath via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Hello all,
>
> we a
I see you also asked this on lldb-commits. This was a better list for that
question, but I responded on the other list. In short, unless you need to use
the MI because you have to support both gdb & lldb, I think you will be much
happier using the SB API's than the MI.
Jim
> On May 26, 2017,
> On May 26, 2017, at 8:17 AM, Pavel Labath via llvm-dev
> wrote:
>
> Hello all,
>
> we are trying to convert some of the lldb tests to lit (for these
> specific tests we are using the googletest format). One of our
> requirements is that we are able to run these tests remotely, so that
> we a
Let me show you a snippet of a lldb debug session in progress in my ObjC
variant:
```
-10,10,v,18.48
Process 45774 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = step in
frame #0: 0x00010e2a multiple.debug`+[Foo
long:int:char:float:](self=Foo, _cmd=,
_param
Because we try as much as possible to let the compiler figure this sort of
thing out for us, we implement the transparent lookups for this & self by
compiling our expression in a context that poses as a method of the class whose
method we are stopped in. For instance, for ObjC, we construct a c
