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

..

esp32

add soft solution for esp32 eco3 live lock issue

2020-08-04 05:50:18 +00:00

esp32s2

esp32s2: IRAM/DRAM memory protection

2020-04-21 15:10:58 +02:00

include/port

esp_system: share abort panic with port layer

2020-03-10 19:56:24 +08:00

CMakeLists.txt

esp32, esp32s2: move panic handling code to new component

2020-03-10 19:56:24 +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-09-04 20:45:38 +02:00