从符号服务器的正确路径加载 PDB 符号？
Loading PDB symbols from symbol server's correct path?
在我们以 x 间隔生成多个构建并将生成的符号文件存储在服务器中的环境中，有没有办法为该特定构建关联符号的正确路径？
您可以使用 symbol server. The association between a DLL/EXE and the PDB is done by the linker who adds a GUID in the DLL/EXE and PDB to match both files，现在像 WPR/WPA 这样的调试器或分析器使用此 GUID 来查找正确的 PDB：
When the linker generates .dll, executable, and PDB files, it stores
identical GUIDs in each file. The GUID is used by tools to determine
if a given PDB file matches a DLL or an executable file. If you alter
a DLL or an executable file—by using a resource editor or copy
protection encoding, or by altering its version information—the GUID
is updated and the debugger cannot load the PDB file. For this reason,
it's very important to avoid manipulating the DLL or executable file
after it is created by the linker.
在我们以 x 间隔生成多个构建并将生成的符号文件存储在服务器中的环境中，有没有办法为该特定构建关联符号的正确路径？
您可以使用 symbol server. The association between a DLL/EXE and the PDB is done by the linker who adds a GUID in the DLL/EXE and PDB to match both files，现在像 WPR/WPA 这样的调试器或分析器使用此 GUID 来查找正确的 PDB：
When the linker generates .dll, executable, and PDB files, it stores identical GUIDs in each file. The GUID is used by tools to determine if a given PDB file matches a DLL or an executable file. If you alter a DLL or an executable file—by using a resource editor or copy protection encoding, or by altering its version information—the GUID is updated and the debugger cannot load the PDB file. For this reason, it's very important to avoid manipulating the DLL or executable file after it is created by the linker.