[Tizen] Add FEATURE_LARGEADDRESS_SUPPORTsubmit/tizen_5.5/20200323.035211submit/tizen/20200323.035150accepted/tizen/unified/20200323.172942accepted/tizen/5.5/unified/20200323.072150

Many diagnostic tools are unaware of 32-bit applications which have
large address spaces (> 2GB). Such tools include the TraceEvent library
(required by PerfView and dotnet-trace), and Visual Studio. They assume
the address range 0x80000000 through 0xFFFFFFFF as the system space and
thus often fail to read symbols from event traces generated by CoreCLR.

This workaround is to support such scenarios by simply discarding MSBs
of 32-bit instruction pointer values in the trace output. Only a minimal
set of values required for symbol resolution are affected by this
change. Beware that you will have to manually restore the original
values when you inspect them in lldb or etc.

1 files changed, 6 insertions, 0 deletions

diff --git a/src/vm/eventpipeblock.cpp b/src/vm/eventpipeblock.cpp
index fb9d6c721e..d510ec8adf 100644
--- a/src/vm/eventpipeblock.cpp
+++ b/src/vm/eventpipeblock.cpp
@@ -457,6 +457,12 @@ bool EventPipeStackBlock::WriteStack(DWORD stackId, StackContents* pStack)
     if (stackSize > 0)
     {
         memcpy(m_pWritePointer, pStack->GetPointer(), stackSize);
+#ifdef FEATURE_LARGEADDRESS_SUPPORT
+        for (int i = 0; i < stackSize / sizeof(UINT_PTR); i++)
+        {
+            ((UINT_PTR*)m_pWritePointer)[i] &= INT_MAX;
+        }
+#endif // FEATURE_LARGEADDRESS_SUPPORT
         m_pWritePointer += stackSize;
     }