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
..
esp32	components/sys: Fix build error about livelock when intwdt is disable	2020-07-23 02:21:32 +00:00
esp32s2	esp_rom: extract common ets apis into esp_rom_sys.h	2020-07-27 15:27:01 +08:00
esp32s3	esp32s3: clk, memory layout	2020-07-27 13:05:22 +08:00
include	esp32, esp32s2: move startup code into esp_system	2020-06-19 18:40:09 +10:00
CMakeLists.txt	esp32, esp32s2: move startup code into esp_system	2020-06-19 18:40:09 +10:00
cpu_start.c	esp_rom: extract common ets apis into esp_rom_sys.h	2020-07-27 15:27:01 +08:00
panic_handler_asm.S	esp32, esp32s2: move panic handling code to new component	2020-03-10 19:56:24 +08:00
panic_handler.c	panic: skip over the first invalid PC in case of InstrFetchProhibited	2020-08-05 12:00:50 +02:00