Crates.io | esp-backtrace |
lib.rs | esp-backtrace |
version | |
source | src |
created_at | 2022-08-09 16:24:15.852696 |
updated_at | 2024-10-10 10:35:45.086592 |
description | Bare-metal backtrace support for Espressif devices |
homepage | |
repository | https://github.com/esp-rs/esp-hal |
max_upload_size | |
id | 641891 |
Cargo.toml error: | TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
Supports the ESP32, ESP32-C2/C3/C6, ESP32-H2, ESP32-P4, and ESP32-S2/S3. Optional exception and panic handlers are included, both of which can be enabled via their respective features.
Please note that when targeting a RISC-V device, you need to force frame pointers (i.e. "-C", "force-frame-pointers",
in your .cargo/config.toml
); this is not required for Xtensa.
You can get an array of backtrace addresses (currently limited to 10) via arch::backtrace()
if
you want to create a backtrace yourself (i.e. not using the panic or exception handler).
When using the panic and/or exception handler make sure to include use esp_backtrace as _;
.
Feature | Description |
---|---|
esp32 | Target ESP32 |
esp32c2 | Target ESP32-C2 |
esp32c3 | Target ESP32-C3 |
esp32c6 | Target ESP32-C6 |
esp32h2 | Target ESP32-H2 |
esp32p4 | Target ESP32-P4 |
esp32s2 | Target ESP32-S2 |
esp32s3 | Target ESP32-S3 |
panic-handler | Include a panic handler, will add esp-println as a dependency |
exception-handler | Include an exception handler, will add esp-println as a dependency |
println | Use esp-println to print messages |
defmt | Use defmt logging to print messages* (check example) |
colors | Print messages in red* |
halt-cores | Halt both CPUs on ESP32 / ESP32-S3 instead of doing a loop {} in case of a panic or exception |
semihosting | Call semihosting::process::abort() on panic. |
custom-halt | Invoke the extern function custom_halt() instead of doing a loop {} in case of a panic or exception |
custom-pre-backtrace | Invoke the extern function custom_pre_backtrace() before handling a panic or exception |
* only used for panic and exception handlers
defmt
FeaturePlease note that defmt
does not provide MSRV guarantees with releases, and as such we are not able to make any MSRV guarantees when this feature is enabled. For more information refer to the MSRV section of defmt
's README:
https://github.com/knurling-rs/defmt?tab=readme-ov-file#msrv
Licensed under either of:
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.