# PolyTracker

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

- Type: Tool
- Targets: Binary
- Category: Debugging and dynamic analysis
- Relationship: Foundation tool
- Sources reviewed: 2026-10-29
- Added to the catalog: 2026-11-09
- Original resource: <https://github.com/trailofbits/polytracker>
- Primary source: <https://github.com/trailofbits/polytracker/blob/ae7b5f12e608f0c9a896cf1af797e4588c7624f9/README.md>
- Catalog page: <https://awesomerea.org/resources/polytracker/>
- Record JSON: <https://awesomerea.org/resources/polytracker/record.json>
- Chinese version: [简体中文](https://awesomerea.org/zh/resources/polytracker/index.md)

## 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.

## Primary sources

1. <https://github.com/trailofbits/polytracker/blob/ae7b5f12e608f0c9a896cf1af797e4588c7624f9/README.md>

## More in Native binaries

- [pyelftools](https://awesomerea.org/resources/pyelftools/index.md) · Tool
- [rustc-demangle](https://awesomerea.org/resources/rustc-demangle/index.md) · Tool
- [Scylla](https://awesomerea.org/resources/scylla/index.md) · Tool
- [TitanEngine Community Edition](https://awesomerea.org/resources/titanengine/index.md) · Tool
- [Volatility 3](https://awesomerea.org/resources/volatility3/index.md) · Tool
- [Decompile-Bench](https://awesomerea.org/resources/decompile-bench-dataset/index.md) · Project

## About this entry

The description was reviewed against primary sources.
Original editorial content: MIT. Linked projects, papers and assets retain their own rights and licenses.