Greg Clayton e91b7957b2 Expose new read memory fucntion through python in SBProcess: ... size_t SBProcess::ReadCStringFromMemory (addr_t addr, void *buf, size_t size, lldb::SBError &error); uint64_t SBProcess::ReadUnsignedFromMemory (addr_t addr, uint32_t byte_size, lldb::SBError &error); lldb::addr_t SBProcess::ReadPointerFromMemory (addr_t addr, lldb::SBError &error); These ReadCStringFromMemory() has some SWIG type magic that makes it return the python string directly and the "buf" is not needed: error = SBError() max_cstr_len = 256 cstr = lldb.process.ReadCStringFromMemory (0x1000, max_cstr_len, error) if error.Success(): .... The other two functions behave as expteced. This will make it easier to get integer values from the inferior process that are correctly byte swapped. Also for pointers, the correct pointer byte size will be used. Also cleaned up a few printf style warnings for the 32 bit lldb build on darwin. llvm-svn: 146636		2011-12-15 03:14:23 +00:00
..
interface	Expose new read memory fucntion through python in SBProcess:	2011-12-15 03:14:23 +00:00
build-swig-Python.sh	Fixed the Xcode project building of LLVM to be a bit more user friendly:	2011-11-04 03:34:56 +00:00
edit-swig-python-wrapper-file.py	Fix remaining Python issues leftover from my previous patch.	2011-06-01 02:33:12 +00:00
finish-swig-Python-LLDB.sh	Fixed the Xcode project building of LLVM to be a bit more user friendly:	2011-11-04 03:34:56 +00:00
modify-python-lldb.py	Add a missing ')' in the comment.	2011-11-08 23:08:03 +00:00
python-extensions.swig	<rdar://problem/10126482>	2011-11-13 06:57:31 +00:00
python-typemaps.swig	I have added a function to SBTarget that allows	2011-12-14 23:49:37 +00:00
python-wrapper.swig	Add more robustness - use PyString_CheckExact(pvalue) to check whether pvalue is a Python string before	2011-12-14 23:27:53 +00:00