Problem: Unknown Frames
You run Hotspots or/and Threading analysis and your application uses a system API intensively
VTunecannot unwind the stack correctly since stacks do not reach user code and stay inside the system modules. Often such stacks may be limited to call sites from system modules. Since
VTunetries to attach incomplete stacks to previous full stacks via
[Unknown frame(s)], you may see
[Unknown frame(s)]hotspots when attributing system layers to user code via the Call stack mode option on the Filter bar.
You run Threading analysis and your application uses synchronization API causing waits that slow down the application
- On Windows, make sure the search directories, specified in theBinary/Symbol Searchdialog box, include paths to PDB files for your application modules. For more details, see the Search Directories topic.
- On Windows, specify paths to the Microsoft* symbol server inTools > Options > Debugging > Symbolspage. On Linux, make sure to install the debug info packages available for your system version. For more details, see the Using Debug Information topic.
- Re-finalize the result.