[vm] Fix stack traces from ASSERT/FATAL.

TEST=vm/dart/symbolized_crash_test
Bug: #60987
Cq-Include-Trybots: luci.dart.try:vm-linux-release-arm64-try,vm-aot-linux-release-arm64-try
Change-Id: I6e1859a99079087161d5af8a10d1728277740218
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/436760
Commit-Queue: Ryan Macnak <[email protected]>
Reviewed-by: Alexander Aprelev <[email protected]>

Author: rmacnak-google

runtime/vm/profiler.cc

@@ -459,6 +459,16 @@ void Profiler::DumpStackTrace(void* context) {
 #endif
 }
 
+// We need the call to DumpStackTrace to be a non-tail call and this function to
+// not get the shrink wrap optimization, otherwise the frame from which we start
+// our stack walk may be clobbered before the stack walk begins.
+#ifdef _MSC_VER
+#pragma optimize("", off)
+#elif __clang__
+__attribute__((optnone))
+#elif __GNUC__
+__attribute__((optimize(0)))
+#endif
 void Profiler::DumpStackTrace(bool for_crash) {
   uintptr_t sp = OSThread::GetCurrentStackPointer();
   uintptr_t fp = 0;
@@ -468,6 +478,9 @@ void Profiler::DumpStackTrace(bool for_crash) {
 
   DumpStackTrace(sp, fp, pc, for_crash);
 }
+#ifdef _MSC_VER
+#pragma optimize("", on)
+#endif
 
 static void DumpCompilerState(Thread* thread) {
 #if !defined(DART_PRECOMPILED_RUNTIME)