IDF version is release/v3.1.
My apllication is very complicate, so I can't describe my code clearly。
This is the whole backtrace, it will occured from time to time.I can't see any function in my application level.
Does anyone have an insight on this issue? thank you very much
backtrace: 40091b78 <invoke_abort>:
40091eb4 <abort>:
40086f38 <lock_acquire_generic>:
4008708c <_lock_acquire_recursive>:
401de8d8 <_vfiprintf_r>:
401d7e80 <fiprintf>:
401d7e10 <__assert_func>:
40099dd4 <vTaskEnterCritical>:
40083810 <esp_pm_impl_switch_mode>:
400839f4 <esp_pm_lock_acquire>:
400839ac <esp_pm_impl_isr_hook>:
40086b00 <_xt_lowint1>:
4026c768 <esp_pm_impl_waiti>:
40162c04 <esp_vApplicationIdleHook>:
4009a5c8 <prvIdleTask>:
4009b764 <vPortTaskWrapper>:
esp32 crashed with unknow reason
-
- Posts: 9719
- Joined: Thu Nov 26, 2015 4:08 am
Re: esp32 crashed with unknow reason
Does this crash happen early in the code? May be a linker issue where the correct lock initialization code for Newlib does not get called...
Re: esp32 crashed with unknow reason
It did not crash in the beginning. After running for a few hours, my application crashed and output the same traceback.
Is it possible that an invalid pointer caused this crash?
Is it possible that an invalid pointer caused this crash?
-
- Posts: 9719
- Joined: Thu Nov 26, 2015 4:08 am
Re: esp32 crashed with unknow reason
Yes, if you got this crash later on it smells like something overwrote some Newlib stub pointers.
Who is online
Users browsing this forum: ignisuti and 73 guests