espressif/esp-idf
1
0
Fork 1
mirror of https://github.com/espressif/esp-idf.git synced 2025-08-09 23:54:33 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'doc/illegalinstruction_on_missing_return' into 'master'

Browse Source 
doc: fatal-errors: note on missing returns and IllegalInstruction

See merge request espressif/esp-idf!16844
This commit is contained in:
morris
2022-01-18 10:21:31 +00:00
parent 0fa3c5b331 31310d46e7
commit 3d899d1c59
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/en/api-guides/fatal-errors.rst
View File

@@ -306,6 +306,8 @@ This CPU exception indicates that the instruction which was executed was not a v
- Some external device has accidentally been connected to the SPI flash pins, and has interfered with communication between {IDF_TARGET_NAME} and SPI flash. - Some external device has accidentally been connected to the SPI flash pins, and has interfered with communication between {IDF_TARGET_NAME} and SPI flash.
- In C++ code, exiting from a non-void function without returning a value is considered to be an undefined behavior. When optimizations are enabled, the compiler will often omit the epilogue in such functions. This most often results in an |ILLEGAL_INSTR_MSG| exception. By default, ESP-IDF build system enables ``-Werror=return-type`` which means that missing return statements are treated as compile time errors. However if the application project disables compiler warnings, this issue might go undetected and the |ILLEGAL_INSTR_MSG| exception will occur at run time.
.. only:: CONFIG_IDF_TARGET_ARCH_XTENSA .. only:: CONFIG_IDF_TARGET_ARCH_XTENSA
InstrFetchProhibited InstrFetchProhibited