esp-idf/components/esp_system
Ivan Grokhotkov 5ff9cd495e 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-08-05 12:00:50 +02:00
..
include coredump: Fixes ESP-specific panic reasons handling 2020-07-27 21:38:33 +03:00
port panic: skip over the first invalid PC in case of InstrFetchProhibited 2020-08-05 12:00:50 +02:00
CMakeLists.txt Merge branch 'bugfix/coredump_esp_panic_reason' into 'master' 2020-07-28 23:49:10 +08:00
component.mk esp_system: restore deleted no stack check flag 2020-07-22 11:57:18 +08:00
Kconfig esp_system: add CONFIG_ESP_SYSTEM_RTC_EXT_CRYS 2020-07-20 11:15:24 +08:00
linker.lf esp32, esp32s2: update console initialization 2020-06-26 15:38:49 +02:00
panic.c coredump: Fixes ESP-specific panic reasons handling 2020-07-27 21:38:33 +03:00
sdkconfig.rename esp_system: add CONFIG_ESP_SYSTEM_RTC_EXT_CRYS 2020-07-20 11:15:24 +08:00
startup.c esp_rom: extract common ets apis into esp_rom_sys.h 2020-07-27 15:27:01 +08:00
system_api.c coredump: Fixes ESP-specific panic reasons handling 2020-07-27 21:38:33 +03:00