Ivan Grokhotkov c3d2942675 panic: skip over the first invalid PC in case of InstrFetchProhibited ... InstrFetchProhibited usually occurs because of a jump to an invalid pointer. In this case, PC in the exception frame is the address of the jump destination. 'esp_ptr_executable' check in print_backtrace function recognizes the first frame as invalid, and the backtrace is interrupted. This prevents the user from finding the location where the invalid pointer is dereferenced. Bypass the 'esp_ptr_executable' check if the exception cause is InstrFetchProhibited. Update the test case to no longer ignore this issue.		2020-09-04 20:45:38 +02:00
..
include	add soft solution for esp32 eco3 live lock issue	2020-08-04 05:50:18 +00:00
port	panic: skip over the first invalid PC in case of InstrFetchProhibited	2020-09-04 20:45:38 +02:00
private_include	esp_system: share abort panic with port layer	2020-03-10 19:56:24 +08:00
CMakeLists.txt	esp32, esp32s2: move reset reason source to esp_system	2020-03-10 19:56:24 +08:00
component.mk	esp_system: share abort panic with port layer	2020-03-10 19:56:24 +08:00
Kconfig	esp32, esp32s2: move panic handling code to new component	2020-03-10 19:56:24 +08:00
linker.lf	esp_system, esp_common: fixes to some panic handler refactor issues	2020-04-24 16:34:15 +08:00
panic.c	esp_system: restore weak esp_reset_reason functions	2020-05-04 10:13:14 +00:00
sdkconfig.rename	esp32, esp32s2: move panic handling code to new component	2020-03-10 19:56:24 +08:00
system_api.c	Include header file soc/cpu.h in memprot.c and system_api.c	2020-07-10 18:21:20 +05:30