pub fn debug_proving_ctx<E, VB>(
vm: &VirtualMachine<E, VB>,
pk: &MultiStarkProvingKey<E::SC>,
ctx: &ProvingContext<E::PB>,
)where
E: StarkEngine,
VB: VmBuilder<E>,
Expand description
Runs the STARK backend debugger to check the constraints against the trace matrices
logically, instead of cryptographically. This will panic if any constraint is violated, and
using RUST_BACKTRACE=1
can be used to read the stack backtrace of where the constraint
failed in the code (this requires the code to be compiled with debug=true). Using lower
optimization levels like -O0 will prevent the compiler from inlining and give better
debugging information.