Setup Native Stack Walks
(Professional and Enterprise only)
To get as detailed call stacks as possible when the native resources tracker is enabled, it is recommended that native stack walker is enabled. In order for the native stack walker to work correctly, the symbols files must be available. To set up the native stack walker and symbol file locations, perform the following steps:
Open the Options window (using Tools->Options).
Make sure the native resources tracker is enabled on the General page (native stacks walks are only available when the native resources tracker is enabled).
Under the Call Stacks settings page, enable the Perform native stack walk option. The stack walk depth can be limited using the Max stack walk depth field.
In order for native stack walks to work correctly, native symbols information must be available. On the Symbol File Locations page, make sure that Retrieve debug symbols from the Microsoft symbols store option is enabled. It is also recommended that symbols files are cached on the local drive.
Now the native stack walker will provide detailed native call stacks when profiling with the native resources tracker enabled.
Note
The first time a stack frame is encountered by the native stack walker, .NET Memory Profiler needs to retrieve information about the frame from the debug symbols. This can take some time, especially if the symbols need to be downloaded. However, the symbol information will be cached by .NET Memory Profiler, which will make subsequent stack walks very much faster.