Tool

PolyTracker

Trace how parser functions consume input bytes by rebuilding programs with LLVM data-flow instrumentation and inspecting the resulting trace.

Targets: Binary
Category: Debugging and dynamic analysis
Relationship: Foundation tool
Sources reviewed: 2026-10-29

Stars: 602
Last commit: 2026-06-10
Language: C++
License (GitHub): Apache-2.0

GitHub data as of 2026-11-09

Copy as Markdown View JSON Cite

Requirements & limits

Needs a target that can be built and instrumented, typically C/C++, plus the specialized LLVM environment. The documented quickstart uses Python tooling and Docker.
Tracing requires rebuilding the target with LLVM instrumentation. Grammar extraction is experimental; host-mounted trace databases can cause severe virtual-machine/container slowdown.

Cite

BibTeX

@misc{polytracker,
  title = {{PolyTracker}},
  howpublished = {\url{https://github.com/trailofbits/polytracker}},
  url = {https://github.com/trailofbits/polytracker},
  urldate = {2026-10-29},
  note = {Awesome REA entry: \url{https://awesomerea.org/resources/polytracker/}}
}

Plain text

PolyTracker. https://github.com/trailofbits/polytracker (accessed 2026-10-29). Awesome REA entry: https://awesomerea.org/resources/polytracker/

Useful? Star Awesome REA on GitHub2.4k

About this entry

The description was reviewed against primary sources.

Report an outdated entry Suggest a translation fix

Primary sources

README.md GitHub · trailofbits/polytracker · Revision ae7b5f1

More in Native binaries

All 502 entries in Native binaries