summaryrefslogtreecommitdiffstats
path: root/lldb/test/class_static
Commit message (Collapse)AuthorAgeFilesLines
* Move some directories to now reside under lang/c or lang/cpp.Johnny Chen2011-06-253-200/+0
| | | | llvm-svn: 133881
* The extra burden for the Python API test case to assign its process object ↵Johnny Chen2011-06-151-5/+3
| | | | | | | | | 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
* Now that we have added a post-processing step for adding truth value testing toJohnny Chen2011-05-241-3/+3
| | | | | | | 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
* Modify the test suite and lldbutil.py to utilize the Python iteration ↵Johnny Chen2011-04-281-2/+1
| | | | | | | | pattern now that the lldb iteration protocol has been added to lldb.py module. llvm-svn: 130452
* Change the rest of lldbutil.py's function names to all lower case formats to ↵Johnny Chen2011-04-271-2/+2
| | | | | | | | be consistent. And modify the test cases accordingly. llvm-svn: 130314
* Converted to use SBProcess.LaunchSimple().Johnny Chen2011-04-191-2/+1
| | | | llvm-svn: 129779
* Centralized a lot of the status information for processes,Greg Clayton2011-04-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Modify test scripts to accomodate SBTarget.Launch() API change.Johnny Chen2011-02-031-1/+1
| | | | llvm-svn: 124828
* Deprecated old forms of SBTarget::Launch. There is not just one and noGreg Clayton2011-01-231-1/+2
| | | | | | SWIG renaming done to work around deprecated APIs. llvm-svn: 124075
* Modify test cases to accomodate Python API change:Johnny Chen2010-12-141-5/+5
| | | | | | | o SBFrame.LookupVar -> FindVariable o SBFrame.LookupVarInScope -> FindValue llvm-svn: 121782
* Add @python_api_test decorator to the remaining Test*.py files.Johnny Chen2010-12-101-0/+2
| | | | llvm-svn: 121448
* For SBTarget.Launch()/LaunchProcess(), there's no need to pass an empty stringJohnny Chen2010-12-081-1/+1
| | | | | | | | | | | | | | 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
* Add comment for a branch of test logic which applies to ['clang', ↵Johnny Chen2010-11-291-0/+1
| | | | | | 'llvm-gcc'] only. llvm-svn: 120355
* Fill in more test sequences for Python API SBFrame.LookupVarInScope(name, ↵Johnny Chen2010-11-192-2/+19
| | | | | | | | | scope). Change SBFrame::LookupVarInScope() to also work with "global" scope in addition to "local" and "parameter" scope. llvm-svn: 119811
* Add Python API tests for file and class static variables, too.Johnny Chen2010-11-181-2/+65
| | | | llvm-svn: 119758
* Add a test for displaying file and class static variables.Johnny Chen2010-11-182-1/+65
| | | | llvm-svn: 119734
* A few modifications to the class arrays test case.Greg Clayton2010-09-131-2/+9
| | | | llvm-svn: 113732
* I made this example after noting that I was unable to display an unsizedGreg Clayton2010-09-132-0/+49
static class array. It turns out that gcc 4.2 will emit DWARF that correctly describes the PointType, but it will incorrectly emit debug info for the "g_points" array where the following things are wrong: - the DW_TAG_array_type won't have a subrange info - the DW_TAG_variable for "g_points" won't have a valid byte size, so even though we know the size of PointType, we can't infer the actual size of the array by dividing the size of the variable by the number of elements. We want to make sure clang and llvm-gcc handle this correctly. llvm-svn: 113730
OpenPOWER on IntegriCloud