microsoft / microsoft/perfview

[TraceEvent] Make SymbolReader extendable for custom symbol formats

Open
#1,282 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
4.7k
Forks
775
Avg merge
5d 11h
Merged PRs (30d)
9

Description

I'm using the TraceEvent library to process events emitted from Delphi code. Sadly the Delphi compiler does not generate pdb files, but some other file formats, e.g. ASCII based *.map files. Hence, my callstacks can't be symbolized with TraceEvent. Clearly, I could implement the symbol lookup code by myself (this is what I'm going to do), but it would be nice if the library could handle other symbol file formats beside pdb as well.

I understand that the focus is on the MS ecosystem but it would be a nice enhancement to the library if the SymbolReader API would be a open to custom implementations.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the SymbolReader API and its existing PDB-based symbol handling. Define how custom symbol-reader implementations would be supplied and determine the API changes needed to support formats such as Delphi ASCII .map files. Done means callers can provide a custom implementation for symbol lookup without changing the library.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
devtools, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.