8000 Updates for #68 · Tomato1107/esp32-snippets@2e05c69 · GitHub
[go: up one dir, main page]

Skip to content

Commit 2e05c69

Browse files
committed
Updates for nkolban#68
1 parent e1040b8 commit 2e05c69

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

cpp_utils/ArduinoBLE.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,4 +42,13 @@ This file can be found in your Arduino IDE installation directories at:
4242

4343
```
4444
<ArduinoIDE>/hardware/espressif/esp32/tools/sdk/include/config
45-
```
45+
```
46+
47+
## Decoding an exception stack trace
48+
While using the BLE C++ classes there is always the unfortunate possibility that something will go wrong and your application crash. Fortunately, this results in some debug information being logged to the console. This is known as a *stack trace*. Included in the stack trace are a sequence of hexadecimal numbers known as the *back trace* which are the list of addresses of functions that were executed just before the crash was detected. If we could decode these we would have a lot of great information that could be used to aid in the resolution. Fortunately there is a fantastic project that makes decoding this information very easy indeed.
49+
50+
This project can be found here:
51+
52+
https://github.com/me-no-dev/EspExceptionDecoder
53+
54+
If you start to encounter crashes in your BLE C++ applications and wish to report these through Github issues, please help us to help you by installing this tool int your Arduino IDE and including the decoded information in the issue report.

0 commit comments

Comments
 (0)
0