OVMS3-idf/components/heap/include
Ivan Grokhotkov c3ae910529 heap: recognize 0x40000000 as an address terminating the backtrace
On Xtensa, backtrace can not recover the two most significant bits of
the address, as the window call size is encoded in these bits.
Because of this, __builtin_return_address modifies these MSBs to
match those of the callee, "fixing" the address. An unfortunate side
effect is that the zero return address, which usually terminates the
backtrace, gets converted to 0x40000000. While there is a valid
instruction at this address, its occurrence in the backtrace is
highly unlikely: this is the first instruction of WindowOverflow4
vector, and IDF apps switch VECBASE to an IRAM location very early at
startup.
2020-04-21 11:48:43 +02:00
..
esp_heap_caps.h Make error codes looks like literals in the code of them (easy for searching). Minor fixes, typos 2018-04-09 13:54:18 +10:00
esp_heap_caps_init.h components/bt: Fix broken API esp_bt_mem_release() for parameter ESP_BT_MODE_BTDM 2018-08-31 14:28:23 +00:00
esp_heap_task_info.h heap: Add task tracking option for heap usage monitoring 2018-02-20 10:32:06 +11:00
esp_heap_trace.h heap: Separate standalone and common part of tracing module 2019-04-01 15:56:15 +03:00
heap_trace.inc heap: recognize 0x40000000 as an address terminating the backtrace 2020-04-21 11:48:43 +02:00
multi_heap.h heap: Fix spurious heap_caps_check_integrity() errors in Comprehensive mode 2017-10-18 15:57:52 +08:00