Hello all
I've recently tracked down a problem in the expression evaluation engine
for lldb, and I'm hoping for some historical context, and possibly some
direction on the most appropriate fix.
## Problem
I'd like to be able to set some target options for the JIT when calling
`expr myRender
Hi
On 03/12/15 18:02, Greg Clayton wrote:
Each expression has a language so we should be able to get the Language* for
renderscript:
lldb_private::Language* language = lldb_private::Language::FindPlugin
(m_expr.GetLanguage());
Then you can add a new virtual class on lldb_private::Langu
Hi All
I'm hoping that someone might be able to give me some direction
regarding `Type` resolution from DWARF informationfor functions taking
anonymous structs hidden behind a typedef
e.g.
```
typedef struct {
int i;
float f;
} my_untagged_struct;
void __attribute__((noinline)) myfunc(m
TypeSP t = type_list->GetTypeAtIndex(i);
+if (t->IsTypedef())
+{
+ type_name_const_str = t->GetName();
+ type_name_cstr = t->GetName().AsCString();
+
(i);
+if (t->IsTypedef())
+{
+ type_name_const_str = t->GetName();
+ type_name_cstr = t->GetName().AsCString();
+}
+}
+
Hi Zachary, Peter
On 30/08/16 00:14, Zachary Turner via lldb-dev wrote:
Right, the existing version that is built and what you are using links
directly against a 2.7 libpython at compile time. So you would probably
need to build LLDB from source and tweak the build system to make it
possible to
