mirror of
https://github.com/rust-embedded/awesome-embedded-rust.git
synced 2026-03-09 07:12:05 -05:00
Where to put panic implementations? #18
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/awesome-embedded-rust#18
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jonas-schievink on GitHub (Apr 30, 2019).
Originally assigned to: @berkus on GitHub.
There's quite a few panic implementations now, so I think it'd be useful to list them here. I'm not sure where exactly they should be put though, because some of them are platform-independent while others aren't. Personally I think these belong in their own section.
List of crates:
panic-halt: Halts the processor on panicspanic-abort: Causes an abort on panics (nightly-only)panic-ramdump: Writes the panic message into the beginning of RAM and enters an infinite loop; the message can be extracted by attaching a debugger (Cortex-M only)panic-semihosting: Prints the panic message via semihosting to an attached debugger (Cortex-M only)panic-itm: Prints the panic through the chip's ITM to a debugger attached to the SWO pin (Cortex-M with ITM only)@jonas-schievink commented on GitHub (May 7, 2019):
Forgot about
panic-never.@Disasm commented on GitHub (May 7, 2019):
Maybe these deserve to be in the panic-section too:
no-panicdont_panic+dont_panic_slice@berkus commented on GitHub (Nov 24, 2024):
PR is ready for review.
@BartMassey commented on GitHub (Nov 25, 2024):
panic-rtt?@berkus commented on GitHub (Nov 28, 2024):
@BartMassey pls review