Expand description
Rust bindings to the Windows ipt.sys driver.
ipt.sys is the Windows kernel driver that manages Intel Processor Trace (Intel PT).
There is no public Microsoft header or documentation for this interface; this crate provides
its own typed request/response layouts for it.
Ipt::open the device, then call one Ipt method per driver operation (e.g.
Ipt::start_process_trace, Ipt::get_trace_buffer). Each method builds its own request,
issues the DeviceIoControl call and decodes the response — no manual buffer/IOCTL plumbing
needed.
§Platform
This crate targets x86_64 on Windows only.
§Stability
ipt.sys is an internal OS component, not a supported public API. Its shape can change between
Windows builds without notice. Treat this crate as best effort, only Microsoft & friends know
how stable this really is.
Structs§
- Address
Filter Range Response - Response to
QueryThreadAddressFilterRange. - Ipt
- Handle to the
ipt.sysdevice, and the entry point for every operation in this crate. - IptOption
- Supplied directly by the caller when starting a trace
(
StartProcessTrace/StartProcessTraceEx), echoed back byQueryProcessTraceConfiguration, and the same layout is written to/read from the registry bySetSystemWideTracingOption/SetPerImageTracingOption. - Trace
Buffer - Output buffer for
Ipt::get_trace_buffer: an 8-byte-aligned byte buffer sized to hold aGetTraceBuffer(opcode 2) response. Iterate the per-thread records it holds withTraceBuffer::iter. - Trace
Buffer Iter - Iterator over a
TraceBuffer’s per-thread trace records, returned byTraceBuffer::iter.
Enums§
- Address
Filter Mode - One IP-filtering range’s mode, as used by the
ConfigureThreadAddressFilterRangerequest’smode.
Constants§
- NUM_
TRIES_ UNLIMITED - Sentinel for
num_triesmeaning “unlimited auto-start attempts”.