| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
llvm-svn: 133878
|
| |
|
|
|
|
|
|
|
| |
to self.process
in order to have its process cleaned up (terminated) upon tearDown is gone for good.
Let's simplify a bunch of Python API test cases.
llvm-svn: 133097
|
| |
|
|
|
|
|
| |
those lldb objects which implement the IsValid() method, let's change the rest of
the test suite to use the more compact truth value testing pattern (the Python way).
llvm-svn: 131970
|
| |
|
|
| |
llvm-svn: 131445
|
| |
|
|
|
|
|
|
| |
no need to check for this
in the testsuite.
llvm-svn: 131443
|
| |
|
|
|
|
|
|
|
| |
OptionGroupVariableObjectDisplay).
Change the boolean "use_dynamic" over to a tri-state, no-dynamic, dynamic-w/o running target,
and dynamic with running target.
llvm-svn: 130832
|
| |
|
|
|
|
|
|
| |
to be consistent.
And modify the test cases accordingly.
llvm-svn: 130174
|
| |
|
|
| |
llvm-svn: 130134
|
| |
|
|
| |
llvm-svn: 129780
|
|
|
for "frame var" and for the
expressions that are simple enough to get passed to the "frame var" underpinnings. The parser code will
have to be changed to also query for the dynamic types & offsets as it is looking up variables.
The behavior of "frame var" is controlled in two ways. You can pass "-d {true/false} to the frame var
command to get the dynamic or static value of the variables you are printing.
There's also a general setting:
target.prefer-dynamic-value (boolean) = 'true'
which is consulted if you call "frame var" without supplying a value for the -d option.
llvm-svn: 129623
|
