All Pro .pdb files are optimized and are stripped of debug symbol information. Therefore my default setting is "Enable Just My Code" to skip the Pro .pdb symbol loading. They have nothing usable in them anyway so this setting helps to speed up the Pro application startup in the debugger. As an example:
'ArcGISPro.exe' (CoreCLR: clrhost): Loaded 'C:\ArcGIS\bin\Extensions\Editing\ArcGIS.Desktop.Editing.dll'.
Skipped loading symbols. Module is optimized and the debugger option
'Just My Code' is enabled.
Usually pdbs dont load if they are missing/cannot be found or dont match the version of the dll they are "paired" with. Perhaps that is the case in your situation? that the debugger is finding older pdbs...?
but, that all said, I am not sure what difference it is making to your debug experience (not loading them) given that all user code/symbol info is optimized away....
Anyway, here's an article from MS - it may hlp u in debugging why your pdbs dont load, espec if u do not want to use the "Just My Code" option:
https://learn.microsoft.com/en-us/visualstudio/debugger/specify-symbol-dot-pdb-and-source-files-in-t...