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
..
build_test	esp_common: allow placing panic handler into IRAM on ESP32-S2	2020-07-22 21:57:58 +02:00
gdb_loadable_elf	CI: Use higher-level interaction with GDB in example tests and test apps	2020-06-05 14:58:34 +00:00
monitor_ide_integration	tools/idf_monitor: add WebSocket client for IDE integration	2020-06-10 10:56:20 +00:00
panic	panic: skip over the first invalid PC in case of InstrFetchProhibited	2020-08-05 12:00:50 +02:00
startup	esp_system: restore deleted no stack check flag	2020-07-22 11:57:18 +08:00