Open dhlsmyx opened 1 month ago
Is it possible your PAT token is expiring faster than you expect?
Note that we don't recommend using PAT tokens as they get logged and can potentially expose your credentials in places that you might not want them logged.
We created new PAT but not working at all.
Is there a workaround to get the cdb.exe work with the Azure Artifacts symbol server?
For now I can just download the pdbs locally from artifacts or cache the symbols from VS, and then run cdb command.
We have a tool using cdb.exe to analyze crash dump automatically with a local symbol server. Since we moved to Azure Artifacts symbol server, it does not work anymore:
This issue is very similar to the one mentioned in this post https://developercommunity.visualstudio.com/t/how-to-use-azure-devops-services-symbol-server-pro/457461#T-N598454
We tried to set the sympath to “https://[user]:[PAT]@[URL]”, but cdb.exe still failed to retrieve symbols (“path not found”).
set _NT_SYMBOL_PATH=cacheC:\WorkSpace\Symbols;srvhttps://msdl.microsoft.com/download/symbols;srv*https://[user]:[PAT]@artifacts.dev.azure.com/{my_org}/_apis/symbol/symsrv
cdb -z “C:\WorkSpace\CrashLogs\sampledmpfile.dmp” -logo “C:\WorkSpace\CrashLogs\sampledmpfile.cdb” -lines -c “.symopt- 100;!sym noisy;!analyze -v;.ecxr;.echo;.echo PARAMETERS:;!for_each_frame dv /t;.echo;.echo CALL_STACK:;kc;.echo;q”
With Visual Studio 2022 we can retrieve published symbols, but just not working with CDB commands.
Anyone experienced the similar issue?