I get a random crash in my project. When searching for REALLY basic stuff like "how the heck do I debug an ESP8266 crash?" I find the ubiquitous reference in the FAQ to a tool called EspExceptionDecoder which I'm apparently too stupid to get to run with PlatformIO. I was able to get GDB to give me some information, however ... but part 1 of this is "Has anyone been able to get EspExceptionDecoder to work with PlatformIO?"
Part 2 is more specific. I get the device to crash fairly regularly in the same place (but not always.)
Fatal exception 28(LoadProhibitedCause)
So far it's always been in an external library but not the same one every time. For instance, once time it looked like it was in WiFi Manager (for which I forgot to record the notes of course) and now it is crashing in NTPClient:
0x40210a5f <NTPClient::sendNTPPacket()+67>: 0x2c38e358
The only consistency between the (so far) two crashes is that it comes when trying to make some sort of network connection. I should also mention at this point that it happens "after a while" and certainly is not every time.
I have put in some debug on the memory:
DEBUG: getFreeHeap(): 34120, getHeapFragmentation(): 2, getMaxFreeBlocks(): 33576
... which stays fairly consistent and shows no weird changes immediately prior to the crash.
I know I have more "typical debug" work to do. It does raise a question in my mind however if network communication in a potentially sub-optimal WiFi network is known to cause issues in standard libraries, and/or if there's a well known (to everyone but me) manner of dealing with it? Since it's popped up in two different libraries with no changes in between, it just makes me wonder.