microsoft / microsoft/winget-cli
Upload debug symbols to Microsoft Symbol Server
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
To debug crashes and perf issues like in #3667 it would be great if the debug symbols would be provided via Microsoft Symbol Server
Proposed technical implementation details
While trying to analyze a ETW trace of the issue in #3667 I noticed that was not able to get the PDB for WindowsPackageManager.dll and this made it hard to tell the user what might cause his high cpu usage.
So when you release a new version (Stable, RC, preview) also upload the PDB so that we users from outside Microsoft can try to debug/analyze the issue first on our own.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how Stable, RC, and preview releases are produced, with particular attention to WindowsPackageManager.dll and its PDB. Use the ETW investigation in #3667 as context. Done means each release's PDB is uploaded to Microsoft Symbol Server and can be retrieved for crash and performance analysis.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100