meshtastic/docs/developers/firmware/stacktrace-decode.mdx
Sacha Weatherstone 9dc879235f
Hardware pages (#299)
* initial devices.json

* initial hardware components

* testing page at /docs/hardware/supported/template

* WIP Changes

* Home page work & updates

* Fix build

* Fix external link button

* Setup linting

* rename, cleanup & lint

* seperate lint cmd for now

Co-authored-by: Foster Irwin <foster@jfirwin.com>
Co-authored-by: Sacha Weatherstone <sachaw100@hotmail..om>
2022-04-02 00:34:49 +11:00

34 lines
850 B
Plaintext

---
id: stacktrace-decode
title: Decoding Stacktraces
sidebar_label: Decoding Stacktraces
---
You may encounter a situation where your device crashes and are left with a stacktrace, below are two methods of decoding them.
## Manual
:::info
This method uses the symbols of the `firmware.elf` file generated from your latest build, you may wish to rebuild to get up-to-date symbols.
:::
First save the backtrace string to a text file:
```text title="backtrace.txt"
Backtrace: 0x....
```
Now run the exception decoder:
```shell
bin/exception_decoder.py backtrace.txt
```
## Real Time
In order to decode stack traces in real time, kep the following command (replacing `DEVICE_PORT` with your device's port) running in your terminal with the suspect device connected
```shell
pio device monitor --port DEVICE_PORT -f esp32_exception_decoder
```