| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
llvm-svn: 133892
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
args, envs, and cwd
from SBProcess.Launch which takes many more arguments that are useless for the test scenario.
llvm-svn: 129776
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
// When stopped on breakppint 1, and then 2, we can get the line entries using
// SBFrame API SBFrame.GetLineEntry(). We'll get the start addresses for the
// two line entries; with the start address (of SBAddress type), we can then
// resolve the symbol context using the SBTarget API
// SBTarget.ResolveSymbolContextForAddress().
//
// The two symbol context should point to the same symbol, i.e., 'a' function.
Add two utility functions to lldbutil.py:
o get_stopped_threads(process, reason):
return the list of threads with the specified stop reason or an empty list if not found
o get_stopped_thread(process, reason):
return the first thread with the given stop reason or None if not found
llvm-svn: 126916
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
SBTarget.LaunchProcess() API.
llvm-svn: 122450
|
|
|
|
|
|
| |
for the two API calls.
llvm-svn: 121898
|
|
|
|
|
|
|
| |
o SBFrame.LookupVar -> FindVariable
o SBFrame.LookupVarInScope -> FindValue
llvm-svn: 121782
|
|
|
|
| |
llvm-svn: 121448
|
|
|
|
|
|
| |
breakpoint, so that when the breakpoint hits, val = 1 instead of 3.
llvm-svn: 120859
|
|
|
|
| |
llvm-svn: 120479
|
|
|
|
|
|
| |
rdar://problem/8710994 Assertion failed: (reg_info) GDBRemoteRegisterContext.cpp, line 199
llvm-svn: 120430
|
|
|
|
| |
llvm-svn: 120352
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the process status is indeed 'stopped' before invoking 'frame variable -t val'
command to inspect the frame variable. When I run the test suite, it sometimes
emits an output like:
runCmd: frame variable -t val
runCmd failed!
error: you must be stopped in a valid stack frame to view frame variables.
The expect() statement inserted is to make sure that the process is stopped and
we have a valid frame.
llvm-svn: 120318
|
|
|
|
|
|
|
|
| |
bits with lldb r117700:
rdar://problem/8584431 Assert in clang while evaluating expression
llvm-svn: 117705
|
|
|
|
| |
llvm-svn: 117278
|
|
|
|
| |
llvm-svn: 117140
|
|
|
|
| |
llvm-svn: 117116
|
|
|
|
| |
llvm-svn: 117101
|
|
|
|
|
|
|
|
|
|
| |
correct
parent call frame information. And comment out the check for stop reason for the
time being. The stop reason disappeared from the "thread backtrace" output for
breakpoint stop with condition.
llvm-svn: 116939
|
|
breakpoint modify -c 'val == 3' 1
after:
breakpoint set -n c
which sets a breakpoint on function 'c'. The breakpoint should only stop if
expression 'val == 3' evaluates to true.
llvm-svn: 116607
|