Rcore Documentation -

The docs don’t pretend you’re writing C. They explain core::arch::global_asm! , extern "C" fn’s, and how to use #[no_mangle] without undefined behavior. If you’re learning Rust and OS dev simultaneously, this is gold.

Because rcore targets memory-constrained devices, stack overflow is a common hazard. The documentation details how to enable guard zones and watermark checking. It also explains how to use the rcore_task_get_stack_usage() function to profile each task's high-water mark. rcore documentation