Anyone familiar with issue of stepping through Rust code with GDB, where jumping to another function causes stack frame corruption or weird issues where stepping takes ages? ```rust #![no_std] #![no_main] use core::panic::PanicInfo; use cortex_r_a::asm::nop; use zynq7000_rt as _; /// Entry point (not called like a normal main function) #[no_mangle] pub extern "C" fn boot_core(cpu_id: u32) -> ! { if cpu_id != 0 { panic!("unexpected CPU ID {}", cpu_id); } let mut var = 0; loop { var += 1; nop(); } main(); } pub fn main() -> ! { let mut var = 0; loop { var += 1; nop(); } } /// Panic handler #[panic_handler] fn panic(_info: &PanicInfo) -> ! { loop {} } ``` When I set a BP at the start of the `boot_core` method, i can step without issues. As soon as I hit the first function which jumps to another function, for exampel `main`, or a `nop` which is not annotated with `#[inline(always)]`, stepping becomes extremely slow, and the call stack display look faulty. In the GDB TUI, I can step without long delays, call stack still looks crap though. In VS Code with cppdbg, stepping takes ages.