Repository navigation
FAQ
Windows PE executables, x64 and x86 (32-bit), built with MSVC, including /O2, /Od, identical-code folding,
/LTCG, PGO and debug builds with incremental linking. Both architectures are measured on the corpus with zero wrong
matches. ELF and ARM64 aren't started.
Yes, with the same commands: pbeta analyze detects a 32-bit PE and records it as machine: x86, and x86 and x64
analyses are never compared with each other. x86 has no .pdata, so every function boundary comes from discovery
(cold PGO blocks are kept with their function, and data in code such as jump tables and /RTCs frame descriptors
isn't decoded). Arguments are inferred from ecx/edx and stack reads, and each hook's calling convention (__cdecl,
__stdcall, __fastcall, __thiscall) comes from its prototype or PDB signature. For the hook host, build the x86
one (Hook Host).
No. Matching works on stripped binaries. With PDBs you get better matching, exact signature and struct-change proposals, argument decoding in the host's log, and much better replay.
Because the engine needs evidence independent of how it found the match, and a hook's criticality may require more than it has (How It Works). An unmatched-looking leaf function with no strings often needs one more check, such as a matched caller or a behavioral pass. Accept it yourself (Review Queue) or add Behavioral Evidence.
Because a wrong pick patches the wrong code. Identical candidates are always ambiguous; you decide.
Yes. The manifest is library-neutral. Use pbeta header to generate hooks.gen.h with each build's RVAs and
patterns, keyed by the exe's SHA-256, or read the repaired manifests yourself.
Not unless you run the AI Proposer with --allow-remote.
No. The analyzer refuses binaries that look packed or protected, and features for defeating integrity checks, anti-tamper or anti-cheat won't be accepted.
- Thresholds in the acceptance policy aren't calibrated yet (
[Guess]in the design doc). -
binddoesn't check that the manifest's RVAs belong to the build it binds to. - Replay needs both builds' PDBs for globals, models only a few imports, and the recorder's size limits are guesses.
Without the
emulatorfeature every case is inconclusive. - The hook host's thunk handles up to 12 parameters and no variadic functions. It can't attach to a running process.
- x86: built-in host actions take at most 128 bytes of stack arguments (handlers have no limit),
skipandreturn <n>need a prototype, and functions/LTCGgave a custom calling convention aren't supported.
Where things stand overall: docs/STATUS.md.
Permanent Beta is Apache-2.0. Found something wrong on this page? Open an issue.
Getting started
Using it
Integrations
Project