-
Notifications
You must be signed in to change notification settings - Fork 8.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tell PublishSymbols task about binaries as well as the PDB files #11852
Conversation
… feed binaries into the indexer engine as well for improved symbol reliability while debugging, especially around thrown exceptions.
Oof. Problem. Have to exclude the packages folder for binaries... Or restrict the search paths to the bin directories or artifacts directories instead of matching everything... |
Hello @zadjii-msft! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
hold please still fixing stuff |
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is crazy to me, but I am totally fine with installing the Windows SDK as part of the build. Wow, though. Just, wow.
) We have been advised to give not only the PDB paths, but paths to the EXE and DLL files we produce, to the PublishSymbols build task. We are assured by our engineering systems teams that enlightening the task to all of this information helps it hook things up better somewhere between our build machine and the symbol server such that debugging is more robust, especially around thrown exception stacks. ## PR Checklist * [x] Closes #11737 - main fix for feeding EXEs and DLLs into the symbol publisher * [x] Closes #11860 - bonus fix because I noticed the PDB source linking wasn't working * [x] I work here. * [x] If it fits, it sits. (cherry picked from commit 52235b0)
) We have been advised to give not only the PDB paths, but paths to the EXE and DLL files we produce, to the PublishSymbols build task. We are assured by our engineering systems teams that enlightening the task to all of this information helps it hook things up better somewhere between our build machine and the symbol server such that debugging is more robust, especially around thrown exception stacks. ## PR Checklist * [x] Closes #11737 - main fix for feeding EXEs and DLLs into the symbol publisher * [x] Closes #11860 - bonus fix because I noticed the PDB source linking wasn't working * [x] I work here. * [x] If it fits, it sits. (cherry picked from commit 52235b0)
We have been advised to give not only the PDB paths, but paths to the EXE and DLL files we produce, to the PublishSymbols build task. We are assured by our engineering systems teams that enlightening the task to all of this information helps it hook things up better somewhere between our build machine and the symbol server such that debugging is more robust, especially around thrown exception stacks.
PR Checklist