Searched refs:canary (Results 1 – 5 of 5) sorted by relevance
131 const uint8_t canary = erase_value; in ZTEST() local159 buf[buf_o - 1] = canary; in ZTEST()160 buf[buf_o + len] = canary; in ZTEST()172 zassert_equal(buf[buf_o - 1], canary, in ZTEST()175 zassert_equal(buf[buf_o + len], canary, in ZTEST()
221 :kconfig:option:`CONFIG_STACK_CANARIES`. If enabled, the compiler will insert a canary223 canary has not been overwritten at function exit. If the check fails, the
882 extra code that inserts a canary value into the stack frame when942 each thread will have its own canary. This makes harder943 to predict the canary location and value.
166 its own stack canary check, but enabling this feature impacts how the compiler
815 * :github:`17586` - stack canary storage area should be read-only to user mode?
