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

..

__init__.py

test_apps: add panic test

2020-05-12 22:27:06 +02:00

test_panic_util.py

panic: skip over the first invalid PC in case of InstrFetchProhibited

2020-08-05 12:00:50 +02:00