Available on crate feature
debug
only.Expand description
Debugging support for probe-rs
The debug
module contains various debug functionality, which can be
used to implement a debugger based on probe-rs
.
Re-exports§
pub use self::debug_step::SteppingMode;
pub use self::stack_frame::StackFrame;
pub use self::variable_cache::VariableCache;
pub use self::debug_info::*;
pub use self::registers::*;
pub use self::variable::*;
Modules§
- Debug information which is parsed from DWARF debugging information.
- Stepping through a program during debug, at various granularities.
- References to the DIE (debug information entry) of functions.
- Target Register definitions, expanded from
crate::core::registers::CoreRegister
to include unwind specific information. - The stack frame information used while unwinding the stack from a specific program counter.
- Information about a Unit in the debug information.
- Variable information used during debug.
- The hierarchical cache of all variables for a given scope.
Structs§
- A specific location in source code. Each unique line, column, file and directory combination is a unique source location.
- A verified breakpoint represents an instruction address, and the source location that it corresponds to it, for locations in the target binary that comply with the DWARF standard terminology for “recommended breakpoint location”. This typically refers to instructions that are not part of the prologue or epilogue, and are part of the user code, or are the final instruction in a sequence, before the processor begins the epilogue code. The
probe-rs
debugger uses this information to identify valid halt locations for breakpoints and stepping.
Enums§
- An error occurred while debugging the target.
- Object reference as defined in the DAP standard.
Functions§
- Generate a unique key that can be used to assign id’s to StackFrame and Variable structs.
Type Aliases§
- A simplified type alias of the
gimli::EndianReader
type.