Jim Ingham cef461772e When building the list of variables we're going to write "using $_lldb_local_vars" ...

statements for, be sure not to include variables that have no locations.  We wouldn't
be able to realize them, and that will cause all expressions to fail.

llvm-svn: 267500

2016-04-26 00:29:59 +00:00

..

CMakeLists.txt

…

DiagnosticManager.cpp

Use Clang's FixItHints to correct expressions with "trivial" mistakes (e.g. "." for "->".)

2016-03-25 01:57:14 +00:00

DWARFExpression.cpp

…

Expression.cpp

…

ExpressionSourceCode.cpp

When building the list of variables we're going to write "using $_lldb_local_vars"

2016-04-26 00:29:59 +00:00

ExpressionVariable.cpp

Collect IRExecutionUnits as part of persistent expression state.

2016-03-21 22:23:38 +00:00

FunctionCaller.cpp

Compilation can end up calling functions (e.g. to resolve indirect functions) so I added

2016-03-21 19:21:13 +00:00

IRDynamicChecks.cpp

…

IRExecutionUnit.cpp

Don't register the addresses of private symbols from expressions.

2016-03-30 03:44:51 +00:00

IRInterpreter.cpp

Fix usage of APInt.getRawData for big-endian systems

2016-04-15 09:55:52 +00:00

IRMemoryMap.cpp

…

LLVMUserExpression.cpp

Breakpoint conditions were making result variables, which they should not do.

2016-04-12 17:17:35 +00:00

Materializer.cpp

…

REPL.cpp

Figure out what the fixed expression is, and print it. Added another target setting to

2016-03-29 22:00:08 +00:00

UserExpression.cpp

Breakpoint conditions were making result variables, which they should not do.

2016-04-12 17:17:35 +00:00

UtilityFunction.cpp

Compilation can end up calling functions (e.g. to resolve indirect functions) so I added

2016-03-21 19:21:13 +00:00