PolyTracker v4.0.0

• Switches from using Sqlite for storing runtime trace information to a custom tdag binary format, resulting in a significant speedup
• Improvements to "blind spot"/file cavity detection
• Numerous bug fixes
• Ability to track file writes to STDOUT and STDERR
• Code cleanup, additional examples, and documentation improvements

PolyTracker v3.1.0

• Instrumentation optimizations that provide a significant runtime speedup
• Metadata and ground-truth control flow information are now stored to the database
• Adds the ability to track multiple input files as well as writes to output files
• Adds an instrumentation-time option to omit control-flow tracking data, providing a significant speedup
• Adds a new feature to map input byte offsets to output byte offsets, e.g., to detect "cavities" in the input file (i.e., regions of the input file that neither affect control flow nor influence a byte written to an output file).

PolyTracker v3.0.1

Bugfix Release

Updates to a newer version of polytracker-llvm that fixes bugs related to taint union propagation.

Various bugfixes related to the Python API for querying databases.

Significant performance improvements in iterating over trace events.

PolyTracker v3.0.0

Major Refactor

• PolyTracker is now divorced from the LLVM/dfsan codebase
• Interactive Python REPL for interacting with tracing
• Instrumentation is stored to a SQLite database at runtime
• Python API to interact with the instrumentation database
• polybuild and polybuild++ can now be run from a host system and will seamlessly build in Docker if necessary

PolyTracker v2.1.0

Various performance and UX improvements. Output JSON schema has changed since the pre-release, but there is now a Python package to parse the output.

Initial Public Release

The initial public release of PolyTracker.