microsoft / microsoft/perfview
TraceEvent symbols missing from MSDL and not pointing to public sources
Open
Nobody has claimed this yet.
Stale
- Dominant language
- C#
- Stars
- 4.7k
- Forks
- 775
- Avg merge
- 5d 11h
- Merged PRs (30d)
- 9
Description
- Only Windows PDBs are published. This means tools like VS Code and dotnet dump can't use them for non-Windows diagnostics.
- The PDBs are only indexed on the internal symbol server.
- They have srcsrv annotations pointing to https://devdiv.visualstudio.com, which customers can't use in VS, and appear to be unusable in OneWatson. Sourcelink pointing to GH might be a better alternative (works on all scenarios mentioned).
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
The issue does not name files or tests. Start by tracing how PerfView's Windows PDBs are published and indexed, then inspect the existing srcsrv or SourceLink configuration. Done means symbols are available for non-Windows diagnostics and source links point to public GitHub sources in the stated scenarios.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github, vscode
- Domain
- build-system, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100