I understand the registers, etc. but I am also curious what SAR, LBEG, LEND and LCOUNT mean.
In addition, is there any chance to get PlatformIO Monitor to print symbolic info, the way IDF Monitor does, essentially pointing out where the crash occurred?
0x40082d1c: _calloc_r at /Users/user/esp/esp-idf/components/newlib/syscalls.c:51
Thanks. I’m using VSCode, so it’s not really something I can use and for the most part, I am really just interested in an explanation what the abbreviations SAR, LBEG, LEND and LCOUNT stand for.
I can’t say for sure I’ved used it myself… I was trying to get exception decoding working a couple months ago, and I did find some way to do it… anyway, worth a try… that and I just found this handy library for saving exceptions as a sort of crash dump log… hopefully it’s not ESP8266 only!
You can use this indirectly to decode a stack trace from PlatformIO, but you do need Arduino installed. However you don’t need to open your PlatformIO project in Arduino, so it is not too hard.
Try this:
Install in the Arduino tools as described in the the me-no-dev git readme.
In PlatformIO build and run your project and get the stack trace ready in the terminal window. This generates the .elf file.
Open in Arduino menu, Tools, ESP Exception Decoder.
You are prompted for a .esp file. Open from /.pio/build/lolin-d32/firmware.elf (or similar)
You are prompted for the trace - paste in from the terminal