summaryrefslogtreecommitdiff
path: root/lldb/tools/debugserver/source/RNBRemote.cpp
diff options
context:
space:
mode:
authorJason Molenda <jason@molenda.com>2021-08-11 17:17:39 -0700
committerJason Molenda <jason@molenda.com>2021-08-11 17:19:31 -0700
commit2b30fc2ff3cadd085f7103cb953cd9cf091ee9b9 (patch)
treea5994db2b7131fab9dfae7de4e776e86ac7068ea /lldb/tools/debugserver/source/RNBRemote.cpp
parent73056f239ef950f3a3e37769c99166306246e9cc (diff)
Fix two bugs with stack corefiles patch, restrict test built debugserver
These two tests, TestSkinnyCorefile.py and TestStackCorefile.py, require a new debugserver on darwin systems to run correctly; for now, skip them if the system debugserver is in use. There's no easy way to test if the debugserver being used supports either of these memory region info features. For end users, the fallback will be a full corefile and that's not the worst thing, but for the tests it is a problem.
Diffstat (limited to 'lldb/tools/debugserver/source/RNBRemote.cpp')
-rw-r--r--lldb/tools/debugserver/source/RNBRemote.cpp1
1 files changed, 1 insertions, 0 deletions
diff --git a/lldb/tools/debugserver/source/RNBRemote.cpp b/lldb/tools/debugserver/source/RNBRemote.cpp
index b70c7ae3707e..dd8b90297995 100644
--- a/lldb/tools/debugserver/source/RNBRemote.cpp
+++ b/lldb/tools/debugserver/source/RNBRemote.cpp
@@ -4311,6 +4311,7 @@ rnb_err_t RNBRemote::HandlePacket_MemoryRegionInfo(const char *p) {
}
ostrm << ";";
if (!region_info.vm_types.empty()) {
+ ostrm << "type:";
for (size_t i = 0; i < region_info.vm_types.size(); i++) {
if (i)
ostrm << ",";