| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
llvm-svn: 133881
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
be consistent.
And modify the test cases accordingly.
llvm-svn: 130314
|
|
|
|
|
|
|
|
| |
args, envs, and cwd
from SBProcess.Launch which takes many more arguments that are useless for the test scenario.
llvm-svn: 129776
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
threads, and stack frame down in the lldb_private::Process,
lldb_private::Thread, lldb_private::StackFrameList and the
lldb_private::StackFrame classes. We had some command line
commands that had duplicate versions of the process status
output ("thread list" and "process status" for example).
Removed the "file" command and placed it where it should
have been: "target create". Made an alias for "file" to
"target create" so we stay compatible with GDB commands.
We can now have multple usable targets in lldb at the
same time. This is nice for comparing two runs of a program
or debugging more than one binary at the same time. The
new command is "target select <target-idx>" and also to see
a list of the current targets you can use the new "target list"
command. The flow in a debug session can be:
(lldb) target create /path/to/exe/a.out
(lldb) breakpoint set --name main
(lldb) run
... hit breakpoint
(lldb) target create /bin/ls
(lldb) run /tmp
Process 36001 exited with status = 0 (0x00000000)
(lldb) target list
Current targets:
target #0: /tmp/args/a.out ( arch=x86_64-apple-darwin, platform=localhost, pid=35999, state=stopped )
* target #1: /bin/ls ( arch=x86_64-apple-darwin, platform=localhost, pid=36001, state=exited )
(lldb) target select 0
Current targets:
* target #0: /tmp/args/a.out ( arch=x86_64-apple-darwin, platform=localhost, pid=35999, state=stopped )
target #1: /bin/ls ( arch=x86_64-apple-darwin, platform=localhost, pid=36001, state=exited )
(lldb) bt
* thread #1: tid = 0x2d03, 0x0000000100000b9a a.out`main + 42 at main.c:16, stop reason = breakpoint 1.1
frame #0: 0x0000000100000b9a a.out`main + 42 at main.c:16
frame #1: 0x0000000100000b64 a.out`start + 52
Above we created a target for "a.out" and ran and hit a
breakpoint at "main". Then we created a new target for /bin/ls
and ran it. Then we listed the targest and selected our original
"a.out" program, so we showed two concurent debug sessions
going on at the same time.
llvm-svn: 129695
|
|
|
|
|
|
|
|
|
| |
output.
Modify test cases in test suite to either expect brief output or to pass -f for full
output as appropriate.
llvm-svn: 124905
|
|
|
|
| |
llvm-svn: 124828
|
|
|
|
|
|
| |
SWIG renaming done to work around deprecated APIs.
llvm-svn: 124075
|
|
|
|
|
|
|
| |
o SBFrame.LookupVar -> FindVariable
o SBFrame.LookupVarInScope -> FindValue
llvm-svn: 121782
|
|
|
|
| |
llvm-svn: 121448
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
as the args and the envs to the launched process.
o lldbtest.py:
Forgot to check in some assertion messages changes for lldbtest.py.
o dotest.py:
Also add "api" category to the default lldb log option list.
llvm-svn: 121220
|
|
|
|
|
|
| |
thread.GetStopReason().
llvm-svn: 118731
|
|
|
|
|
|
|
|
| |
asserting:
thread.GetStopReason() == lldb.eStopReasonBreakpoint
llvm-svn: 118713
|
|
|
|
|
|
|
|
| |
test method when asserting:
thread.GetStopReason() == lldb.eStopReasonBreakpoint
llvm-svn: 118711
|
|
|
|
|
|
| |
accommodate.
llvm-svn: 116705
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
debug information and you evaluated an expression, a crash would occur as a
result of an unchecked pointer.
Added the ability to get the expression path for a ValueObject. For a rectangle
point child "x" the expression path would be something like: "rect.top_left.x".
This will allow GUI and command lines to get ahold of the expression path for
a value object without having to explicitly know about the hierarchy. This
means the ValueObject base class now has a "ValueObject *m_parent;" member.
All ValueObject subclasses now correctly track their lineage and are able
to provide value expression paths as well.
Added a new "--flat" option to the "frame variable" to allow for flat variable
output. An example of the current and new outputs:
(lldb) frame variable
argc = 1
argv = 0x00007fff5fbffe80
pt = {
x = 2
y = 3
}
rect = {
bottom_left = {
x = 1
y = 2
}
top_right = {
x = 3
y = 4
}
}
(lldb) frame variable --flat
argc = 1
argv = 0x00007fff5fbffe80
pt.x = 2
pt.y = 3
rect.bottom_left.x = 1
rect.bottom_left.y = 2
rect.top_right.x = 3
rect.top_right.y = 4
As you can see when there is a lot of hierarchy it can help flatten things out.
Also if you want to use a member in an expression, you can copy the text from
the "--flat" output and not have to piece it together manually. This can help
when you want to use parts of the STL in expressions:
(lldb) frame variable --flat
argc = 1
argv = 0x00007fff5fbffea8
hello_world._M_dataplus._M_p = 0x0000000000000000
(lldb) expr hello_world._M_dataplus._M_p[0] == '\0'
llvm-svn: 116532
|
|
|
|
| |
llvm-svn: 116490
|
|
|
|
|
|
|
|
| |
about 'expr var',
not 'frame variable var'.
llvm-svn: 116419
|
|
|
|
|
|
| |
function to get the line number to break on during setUp().
llvm-svn: 116275
|
|
|
|
|
|
| |
module.
llvm-svn: 115922
|
|
|
|
|
|
|
| |
a base of 0 so that the radix of the string is determined based on the contents
of string.
llvm-svn: 114764
|
|
|
|
| |
llvm-svn: 114739
|
|
|
|
|
|
| |
been fixed.
llvm-svn: 113750
|
|
|
|
|
|
|
|
|
|
| |
method where they belong. Also fixed a logic error in maintaining the command
interface flag (runStarted) indicating whether the lldb "run"/"process launch"
command has been issued. It was erroneously cleared.
Modified the test cases to take advantage of the refactoring.
llvm-svn: 112863
|
|
|
|
| |
llvm-svn: 112824
|
|
|
|
| |
llvm-svn: 112732
|
|
|
|
|
|
|
|
| |
argument when issuing a "run" lldb command within the test case meant to
exercise the Python APIs, but is using the command interface due to certain
reason (such as target.LaunchProcess() does not reliably bring up the inferior).
llvm-svn: 112682
|
|
|
|
| |
llvm-svn: 112646
|
|
|
|
|
|
|
|
| |
breakpoint by FileSpec and line number and exercises some FileSpec APIs.
Also, RUN_STOPPED is a bad assert name, RUN_SUCCEEDED is better.
llvm-svn: 112327
|
|
|
|
|
|
|
| |
and process. Added comment within the file about issues of using LaunchProcess
of SBTarget to launch a process (rdar://problem/8364687).
llvm-svn: 112276
|
|
|
|
|
|
| |
Added a utility method to TestBase class to debug print an SBValue object.
llvm-svn: 112247
|
|
|
|
| |
llvm-svn: 111960
|
|
|
|
| |
llvm-svn: 111939
|
|
"variable list bits" display bits variable correctly, but not "variable list".
llvm-svn: 111937
|