diff options
| author | Howard Hellyer <hhellyer@uk.ibm.com> | 2016-07-18 08:25:59 +0000 |
|---|---|---|
| committer | Howard Hellyer <hhellyer@uk.ibm.com> | 2016-07-18 08:25:59 +0000 |
| commit | 97be487728c242feb197410872ca191fc5f5de0f (patch) | |
| tree | e1f11eb6c69ee30bbc5ef57f8572e79c8a71ec24 /llvm/test/CodeGen/AMDGPU/promote-alloca-shaders.ll | |
| parent | 6731f13458884f8fc8cf55706d5e4ac06daa6d5c (diff) | |
| download | bcm5719-llvm-97be487728c242feb197410872ca191fc5f5de0f.tar.gz bcm5719-llvm-97be487728c242feb197410872ca191fc5f5de0f.zip | |
Implement GetMemoryRegions() for Windows Minidumps and live processes.
Summary:
This patch fills in the implementation of GetMemoryRegions() on the Windows live process and minidump implementations of lldb_private::Process (ProcessWindowsLive::GetMemoryRegionInfo and ProcessWinMiniDump::Impl::GetMemoryRegionInfo.) The GetMemoryRegions API was added under: http://reviews.llvm.org/D20565
The existing Windows implementations didn’t fill in the start and end addresses within MemoryRegionInfo. This patch fixes that and adds support for the new mapped flag on MemoryRegionInfo that says whether a memory range is mapped into the process address space or not.
The behaviour of both live and core implementations should match the behaviour documented on Process::GetMemoryRegionInfo (in Process.h) which in turn should match the behaviour of the qMemoryRegionInfo query documented in lldb-gdb-remote.txt.
Reviewers: clayborg, amccarth
Subscribers: amccarth, lldb-commits
Differential Revision: https://reviews.llvm.org/D22352
llvm-svn: 275778
Diffstat (limited to 'llvm/test/CodeGen/AMDGPU/promote-alloca-shaders.ll')
0 files changed, 0 insertions, 0 deletions
