Set up Windows Debugger (WinDbg) or Visual Studio to resolve Unity symbols so you can debug your Unity applications or the Unity Editor.
If your debugging tool is already set up to resolve Unity symbols and you want to know how to set up live or forensic debugging, refer to:
Follow these instructions to configure Windows Debugger (WinDbg) to automatically download and resolve Unity store symbols. When WinDbg has access to these symbols, you can use it to debug your application or the Editor.
Unity.exe
..sympath+ SRV*c:\symbols-cache*http://symbolserver.unity3d.com/
As a result, WinDbg is ready to debug your Unity Editor or application.
.sympath+ SRV*c:\symbols-cache*http://symbolserver.unity3d.com/
.sympath
on its own sets a new symbol path, which overwrites the previous path. The +
addition ignores the existing symbol path, and appends the symbol store lookup.
The SRV
indicates a remote server to fetch from. The c:\symbols-cache
is a local path to cache the downloaded symbols. Before WinDbg retrieves symbols, it checks that path first so it doesn’t download the same symbol multiple times. You can change this path to any directory on your system.
This is the URL of the symbol store which your debugging software will fetch from.
Follow these instructions to configure Visual Studio (2019 or later) to automatically download and resolve Unity store symbols. When Visual Studio has access to these symbols, you can use it to debug applications or the Editor.
https://symbolserver.unity3d.com/
into the new list entry.Visual Studio is ready to debug your Unity code.