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
..
build_test	esp32s2: fix when enable multi phy init data bin compile err.	2020-03-11 18:03:21 +08:00
gdb_loadable_elf	Add JTAG related example tests	2020-05-05 11:08:33 +02:00
panic	panic: skip over the first invalid PC in case of InstrFetchProhibited	2020-09-04 20:45:38 +02:00
startup	Merge branch 'bugfix/inline_get_cpu_id_hal_func' into 'master'	2020-03-26 18:14:51 +08:00