summaryrefslogtreecommitdiffstats
path: root/lldb/test/python_api/process/main.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Add a test sequence of SBProcess.ReadCStringFromMemory() with (char ↵Johnny Chen2011-12-161-0/+1
| | | | | | | | *)my_char_ptr as the address to read from. char *my_char_ptr = (char *)"Does it work?"; llvm-svn: 146716
* Add test scenario for newly added SBProcess APIs: ReadCStringFromMemory() ↵Johnny Chen2011-12-151-0/+3
| | | | | | and ReadUnsignedFromMemory(). llvm-svn: 146704
* Add an API SBProcess::GetByteOrder() and add test cases which utilizes ↵Johnny Chen2011-03-011-0/+2
| | | | | | | | | GetByteOrder(), among other SBProcess APIs, to write (int)256 into a memory location of a global variable (int)my_int and reads/checks the variable afterwards. llvm-svn: 126792
* Add TestProcessAPI.py which exercises some Python SBProcess API. In ↵Johnny Chen2011-03-011-0/+25
particular, this tests the SBProcess.ReadMemory() API, which, due to SWIG typemap'ing, expects 3 arguments (the location to read from, the size in bytes to read, and an SBError object), and returns the result as a Python string object. On SnowLeopard where this has been tested, the SWIG script needs to be pampered (use the exact same parameter names as in SBProcess.h) in order for this to work. llvm-svn: 126736
OpenPOWER on IntegriCloud