Fix a couple minor typos in $qMemoryRegionInfo packet docs.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@210163 91177308-0d34-0410-b5e6-96231b3b80d8
Add gdb-remote test to ensure $qMemoryRegionInfo is supported.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@210185 91177308-0d34-0410-b5e6-96231b3b80d8
Add gdb-remote test for $qMemoryRegionInfo code querying.

Added test stub for collecting a code, heap and stack address.

Added test to verify that the code address returns a readable,
executable memory region and that the memory region range
was indeed the one that the code belonged to.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@210187 91177308-0d34-0410-b5e6-96231b3b80d8
Added gdb-remote $qMemoryRegionInfo tests for heap and stack.

Added two new tests: one to verify that a test exe heap address
returned is readable and writeable, and a similar one to verify
a test exe stack address is readable and writeable.

Ran the main.cpp test exe code through the Xcode re-indenter.
I was using TextMate to edit the test's C++ code alongside the
Python code but last check-in found that it was not handling
tabs/indentation the way I am intending it.

Modified test exe to require C++11.

Refactored gdb remote python code's handling of memory region
info into more re-usable methods.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@210196 91177308-0d34-0410-b5e6-96231b3b80d8
Merge upstream llvm.org r210196 into dev-tfiala-native-protocol-linux-x86_64
Move MemoryRegionInfo out of Target/Process.h into its own header.

lldb-gdbserver and NativeProcessProtocol will use MemoryRegionInfo
but don't want to pull in Process.h.  Pull this declaration and
definition out into its own header.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@210213 91177308-0d34-0410-b5e6-96231b3b80d8
Merge upstream llvm.org r210213 into dev-tfiala-native-protocol-linux-x86_64

Conflicts:
	lldb.xcodeproj/project.pbxproj
Added generic $qMemoryRegionInfo support.

llgs now handles $qMemoryRegionInfo assuming the NativeProcessProtocol
implements the new GetMemoryRegionInfo() interface.

The test for support for $qMemoryRegionInfo requires a process to be debugged
to answer correctly.  If a process is currently being debugged, it will test
reading address 0, which should not produce an error unless the feature
is unsupported.

The default impl returns an error indicating that it is not supported.

The Linux impl is a TODO in the WIP check-in.