Searched refs:guard (Results 26 – 46 of 46) sorted by relevance
12
169 #no support of -mstack-protector-guard=global"
74 by preceding all stack areas with a 4K guard page.
161 memories, and/or programs a stack-overflow MPU guard at the bottom of the thread's415 the stack guard (in certain Arm v8-M configurations with :kconfig:option:`CONFIG_MPU_GAP_FILLING`416 enabled 2 MPU regions are required to implement the guard feature)499 * a read-only region for the MPU stack guard
198 by preceding all stack areas with a fixed guard region.
206 implemented via dedicated CPU features, or read-only MMU/MPU guard regions
99 the thread's guard region to always guarantee stack overflow detection,
63 Some systems implement this feature by creating at runtime a 'guard' MPU region
178 - If guard-based stack overflow detection is enabled, a small write-protected
260 * :github:`3718` - Mpu stack guard is not set when reaching main
153 * :github:`16779` - [Zephyr v1.14] ARM: fix the start address of MPU guard in stack-fail checking (…353 * :github:`16779` - [Zephyr v1.14] ARM: fix the start address of MPU guard in stack-fail checking (…597 - Fix and normalize headers guard
69 * arch: arm: thread built-in stack guard implementation
964 * :github:`16779` - [Zephyr v1.14] ARM: fix the start address of MPU guard in stack-fail checking (…
261 * Added kconfig :kconfig:option:`CONFIG_XTENSA_BREAK_ON_UNRECOVERABLE_EXCEPTIONS` to guard
258 memory) and stack guard features.
96 resulting sample point outside the guard limit.
429 * Added a guard to prevent bonding to the same device more than once.
900 dynamic MPU regions (user thread stack, PRIV stack guard
202 mapped with guard pages on both ends to catch undesired
1203 We guard all access to services using a custom security check implemented in
153 …<https://wiki.sei.cmu.edu/confluence/display/c/PRE06-C.+Enclose+header+files+in+an+include+guard>`_
1141 # for example, stack guard (if enabled). So the libc partition must be pinned
