Right now it's impossible to view Mono stack frames within a recorded WPR trace (they show up as ?!?, like the documentation says).

Can this tool be extended to allow viewing them in Windows Performance Analyzer?

The latest Version 2.7 which introduces support for VS 2022 cannot be installed on previous versions.

With only 2019 installed, it gives this error:

VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.

This should fix an issue where pmip file parsing fails if your system is configured with a decimal separator that is not .. On my system I had , set as the decimal separator (default for danish region setting) and managed addresses were not translated but as soon as I set it to . it started working.

This is mostly a speculative fix since I'm not actually sure how to build/package the extension in order to load it into VS so I haven't tested it beyond trying to parse some different version numbers with different decimal separators configured.

I set UNITY_MIXED_CALLSTACK environment variable 1, set Just My Code disabled in visual studio. set the symbol path in vs is http://symbolserver.unity3d.com/.

Then, I made a Unity2019.4.8f1's dump file, and go to Analyse it , but the callstack of managed code is not show

callstack :

0000012c2897c953() 0000012c25ab4788() mono-2.0-bdwgc.dll!mono_jit_runtime_invoke(_MonoMethod * method, void * obj, void * * params, _MonoObject * * exc, _MonoError * error) 行 2809 C mono-2.0-bdwgc.dll!do_runtime_invoke(_MonoMethod * method, void * obj, void * * params, _MonoObject * * exc, _MonoError * error) 行 2921 C [内联框架] mono-2.0-bdwgc.dll!mono_runtime_try_invoke(_MonoMethod *) 行 3026 C mono-2.0-bdwgc.dll!mono_runtime_invoke(_MonoMethod * method, void * obj, void * * params, _MonoObject * * exc) 行 2968 C Unity.exe!scripting_method_invoke(class ScriptingMethodPtr,class ScriptingObjectPtr,struct ScriptingArguments &,class ScriptingExceptionPtr *,bool) Unity.exe!ScriptingInvocation::Invoke(class ScriptingExceptionPtr *,bool) Unity.exe!MonoBehaviour::CallMethodIfAvailable(int) Unity.exe!MonoBehaviour::CallUpdateMethod(int) Unity.exe!BaseBehaviourManager::CommonUpdate(void) Unity.exe!BehaviourManager::Update(void) Unity.exe!InitPlayerLoopCallbacks'::2'::UpdateScriptRunBehaviourUpdateRegistrator::Forward() Unity.exe!ExecutePlayerLoop(struct NativePlayerLoopSystem *) Unity.exe!ExecutePlayerLoop(struct NativePlayerLoopSystem *) Unity.exe!PlayerLoop(void) Unity.exe!PlayerLoopController::UpdateScene(bool) Unity.exe!Application::TickTimer(void) Unity.exe!MainMessageLoop() Unity.exe!WinMain() Unity.exe!__scrt_common_main_seh() kernel32.dll!BaseThreadInitThunk() ntdll.dll!RtlUserThreadStart()

c# code :

public class NewBehaviourScript : MonoBehaviour { // Start is called before the first frame update void Start() {

}

// Update is called once per frame
void Update()
{
    if(Input.GetKeyDown(KeyCode.A)) {
        int i = 0;
        while(true) {
            ++i;
        }
    }   
}

}

I don't understand why , so i need help

Added initial support for Visual Studio 2022. Tested with recent trunk with both 2019 and 2022.

2 things that may need cleanup :

1. Getting Visual Studio path seems a bit tricky. Used my local path for now.
2. VSIX Manifest needs comment/uncomment depending on version building for.

Need to bump extension version after landing fix: https://github.com/Unity-Technologies/UnityMixedCallstack/commit/627053efe0a69ce2f034bafe75e95d5dd5d9232d