Crates.io | vex-libunwind |
lib.rs | vex-libunwind |
version | 0.1.0 |
source | src |
created_at | 2024-09-19 02:47:42.905595 |
updated_at | 2024-09-19 02:47:42.905595 |
description | Idiomatic Rust bindings for LLVM libunwind on VEX V5 robots |
homepage | https://vexide.dev |
repository | https://github.com/vexide/vex-libunwind |
max_upload_size | |
id | 1379801 |
size | 14,940 |
Idiomatic Rust bindings for LLVM libunwind on VEX V5 robots
cargo add --git https://github.com/vexide/vex-libunwind.git
To unwind from the current execution point, also known as "local" unwinding, capture the current CPU state with UnwindContext
and then step through each stack frame with an UnwindCursor
.
let context = UnwindContext::new().unwrap();
let mut cursor = UnwindCursor::new(&context);
loop {
// Print instruction pointer (i.e. "program counter")
println!("{:?}", cursor.register(registers::UNW_REG_IP));
if !cursor.step().unwrap() {
// End of stack reached
break;
}
}
Libunwind will not find stack frames unless you add unwind tables to your program and show it where to find them.
Add unwind tables by updating your target file or using the -Cforce-unwind-tables=on
rust flag:
{
...,
"default-uwtable": true
}
Then update your target file to include the unwind tables and the symbols libunwind uses to find them:
SECTIONS {
/* ... */
.eh_frame : {
__eh_frame_start = .;
*(.eh_frame)
__eh_frame_end = .;
} > RAM
.eh_framehdr : {
__eh_frame_hdr_start = .;
*(.eh_framehdr)
__eh_frame_hdr_end = .;
} > RAM
.ARM.exidx : {
__exidx_start = .;
*(.ARM.exidx*)
*(.gnu.linkonce.armexidix.*.*)
__exidx_end = .;
} > RAM
/* ... */
}
Documentation for LLVM-flavored libunwind: https://github.com/llvm/llvm-project/blob/main/libunwind/docs/index.rst
Documentation for similar but distinct libunwind/libunwind project: