> On Jun 19, 2016, at 12:25 AM, Hal Finkel wrote:
>
> a) LLVM has a time-based release cycle, not a schedule-based one. As such, a
> simple and predictable version number makes sense.
> b) The LLVM project as a whole is a lot bigger than LLVM IR, even given its
> centrality to the project in
The variables are available through the frame in your symbol context. You have
a line of code commented out in your script:
#variable = frame.GetVariables(target,True,True,True)
Change it to:
get_arguments = True # Get argument variables
get_locals = True # Get local variabl
The right way to do this is to say "I want a GDB server port for user space
process 123". The python would then start up a socket that can be connected to
that can vend the information about the user space process directly through a
dedicated GDB server port. Memory reads would translate the mem
We don't tend to look at the GDB built gdbserver at all. Feel free to submit
patches to fix anything or add support for anything that gdbserver doesn't
have. We are open to changes, but they are not a priority since we have our own
lldb-server and debugserver on MacOSX.
Greg Clayton
> On Jun 1
Hi!
Unfortunately, this is a regression introduced in r251082. From that moment
lldb-mi requires LLDB_DISABLE_PYTHON=0 for showing wide chars:
char16/char32 types.
If you cannot enable python support, I suggest you to:
1. ignore MI_add_summary's errors by returning TRUE:
```
Index: tools/lldb-mi/
