Expand description
Records the debuggerβs opcode steps straight into a SolDB step table.
Re-exportsΒ§
use alloy_primitives::U256;πuse evm2::EvmTypes;πuse evm2::Inspector;πuse evm2::evm::JournalEntry;πuse evm2::interpreter::InstrStop;πuse evm2::interpreter::Interpreter;πuse evm2::interpreter::Message;πuse evm2::interpreter::MessageResult;πuse evm2::interpreter::op;πuse evm2::interpreter::opcode::OpCode;πuse foundry_evm_traces::debug::DebugRecording;πuse foundry_evm_traces::debug::DebugStepSink;πuse foundry_evm_traces::debug::RecordedFrame;πuse foundry_evm_traces::debug::StepConverter;πuse foundry_evm_traces::debug::step_record;πuse soldb_core::EvmWord;πuse soldb_core::StepRecord;πuse soldb_core::StepTable;πuse std::fmt;πuse std::sync::Arc;π
StructsΒ§
- Debug
Recorder - Records every opcode step of the debugged calls into a [
StepTable], with the steps that each call and creation spans. - Open
Frame π - A frame that runs now.
- Pending
Step π - What a step records when it starts.
ConstantsΒ§
- STORAGE_
INPUTS π - The most stack words the storage opcodes read:
SSTOREandTSTOREread the slot and the value.
FunctionsΒ§
- changed π
- The range where
newdiffers fromold, which has the same length. - copy_
steps π - Appends
stepsofsourcetotarget,deeperlevels deeper. - memory_
write π - The destination a memory-writing opcode takes from its pre-execution stack. Memory-reading opcodes can expand memory but leave all new bytes zero.