If you see functions named “unknown” in the PIX UI, make sure that you are not using FASTLINK<\/em> PDBs. The following figure shows the \/DEBUG:FULL<\/em> linker option in the Visual Studio UI.<\/p>\n <\/p>\n If you\u2019re profiling on the same machine you just built your title on, the path to the PDB that the compiler stored in your title\u2019s modules is typically all PIX needs to locate the PDB. However, there are scenarios in which you\u2019ll need to explicitly tell PIX where your PDBs are located. This situation often occurs if you\u2019re profiling your title on a different machine than the one used to build it. In this case, you can point PIX to your PDBs either by setting the _NT_SYMBOL_PATH environment variable, or by using the PDB Search Paths<\/strong> option on PIX\u2019s Settings page. If you’re using the _NT_SYMBOL_PATH environment variable to configure PIX to find your PDBs, remember to check the Use _NT_SYMBOL_PATH<\/strong> checkbox on the Settings page.<\/p>\n <\/p>\n You may also find it useful to configure PIX so that it can access the PDBs for the Windows OS components supplied by Microsoft. Configuring PIX in this way will give you more complete callstacks in Timing Captures<\/a>, for example.<\/p>\n To configure PIX to access the Windows OS symbols, add the URL to the Microsoft symbol server (srv*c:\\symcache*https:\/\/msdl.microsoft.com\/download\/symbols) as shown in the following screenshot.<\/p>\n If you make changes to your symbol path settings while a Timing Capture<\/a> is open, use the Reload Symbols<\/strong> menu option on the Manage Symbols<\/strong> menu in the upper left corner of the capture to cause PIX to re-process the symbols.<\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/pix\/wp-content\/uploads\/sites\/41\/2021\/02\/pix_cpu_pdb_full-1.png\")
<\/a><\/p>\nSetting symbol paths<\/h3>\n
<\/a><\/p>\n<\/a><\/p>\nReloading symbols<\/h3>\n