From 95d1fb9897921cb8a654d1426a0a16f522e95508 Mon Sep 17 00:00:00 2001
From: Per Lindgren <per.lindgren@ltu.se>
Date: Fri, 4 Jan 2019 08:39:06 +0100
Subject: [PATCH] bt broken?
---
examples/panic.rs | 29 +++++++++++++++++++++++++++++
1 file changed, 29 insertions(+)
create mode 100644 examples/panic.rs
diff --git a/examples/panic.rs b/examples/panic.rs
new file mode 100644
index 0000000..9738eaf
--- /dev/null
+++ b/examples/panic.rs
@@ -0,0 +1,29 @@
+//! Changing the panicking behavior
+//!
+//! The easiest way to change the panicking behavior is to use a different [panic handler crate][0].
+//!
+//! [0]: https://crates.io/keywords/panic-impl
+
+#![no_main]
+#![no_std]
+
+// Pick one of these panic handlers:
+
+// `panic!` halts execution; the panic message is ignored
+// extern crate panic_halt;
+// extern crate panic_abort;
+
+// Reports panic messages to the host stderr using semihosting
+// NOTE to use this you need to uncomment the `panic-semihosting` dependency in Cargo.toml
+extern crate panic_semihosting;
+
+// Logs panic messages using the ITM (Instrumentation Trace Macrocell)
+// NOTE to use this you need to uncomment the `panic-itm` dependency in Cargo.toml
+// extern crate panic_itm;
+
+use cortex_m_rt::entry;
+
+#[entry]
+fn main() -> ! {
+ panic!("Oops")
+}
--
GitLab