cdbe594841
No need to pass an empty string as an arg or as an env string to the SBTarget.LaunchProcess() API.
...
llvm-svn: 122450
2010-12-22 22:56:19 +00:00
763d1a17a1
Fix typos in SBBreakpoint::GetThreadIndex()/GetThreadName(), and test sequences
...
for the two API calls.
llvm-svn: 121898
2010-12-15 21:39:37 +00:00
94f928b83f
Modify test cases to accomodate Python API change:
...
o SBFrame.LookupVar -> FindVariable
o SBFrame.LookupVarInScope -> FindValue
llvm-svn: 121782
2010-12-14 18:59:15 +00:00
a47d7cb9b9
Add @python_api_test decorator to the remaining Test*.py files.
...
llvm-svn: 121448
2010-12-10 01:21:27 +00:00
038d436ac8
Test that "breakpoint modify -c ''" clears the condition for the last created
...
breakpoint, so that when the breakpoint hits, val = 1 instead of 3.
llvm-svn: 120859
2010-12-03 23:57:17 +00:00
1922a8dbea
Remove @skip decorators for fixed crashes.
...
llvm-svn: 120479
2010-11-30 22:34:19 +00:00
aa9bc2eca5
Entire test class skipped due to:
...
rdar://problem/8710994 Assertion failed: (reg_info) GDBRemoteRegisterContext.cpp, line 199
llvm-svn: 120430
2010-11-30 17:35:58 +00:00
11d2bae187
Minor comment fix.
...
llvm-svn: 120352
2010-11-29 23:47:40 +00:00
c9ea0f8425
Add an expect() statement within breakpoint_conditions() method which tests that
...
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
2010-11-29 20:49:09 +00:00
b00c8e83dd
Remove the @expectedFailure as the following bug is fixed with newer clang bits with lldb r117700:
...
rdar://problem/8584431 Assert in clang while evaluating expression
llvm-svn: 117705
2010-10-29 20:28:28 +00:00
ae5de9b269
Skip this test module for the time being until we get a newer clang on lldb tot.
...
llvm-svn: 117278
2010-10-25 18:26:20 +00:00
d9bebeb2be
Comment out the debug statement for printing the SBBreakpoint object.
...
llvm-svn: 117140
2010-10-22 20:08:56 +00:00
5bfb8ee64e
Add test case for using SBBreakpointLocation to set break condition.
...
llvm-svn: 117116
2010-10-22 18:10:25 +00:00
962b799070
Fix misnamed test method names.
...
llvm-svn: 117101
2010-10-22 16:17:39 +00:00
2e431cea84
Make the breakpoint condition test more robust with regard to checking the 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
2010-10-20 18:38:48 +00:00
27b107b800
Add a test case for exercising breakpoint conditions using the lldb command:
...
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
2010-10-15 18:52:22 +00:00
Johnny Chen