Lines Matching refs:will
47 * **Linker scripts and toolchains**: architecture-specific details will most
274 will not function as intended and will experience bizarre crashes, mostly due
541 Such carve-outs will always be tracked in ``thread.stack_info.start``.
624 on write. Reserved memory will be used for the guard region.
633 into the address space. The stack object will still need to be properly aligned
674 implies that :c:macro:`ARCH_THREAD_STACK_SIZE_ADJUST()` will need to round
713 extra stack memory. An overflow will eventually crash into the guard region.
715 * If the thread is running in user mode, a memory protection region will be
717 before or after it. An overflow in user mode will crash into the privilege
719 handling a system call will crash into the guard region.
722 will be mapped into kernel memory, and the stack buffer in the user part of
729 :c:macro:`ARCH_THREAD_STACK_RESERVED` will need to be defined to capture
790 * :c:func:`arch_user_mode_enter` which will irreversibly drop a supervisor
840 inaccessible to user threads at all times. This stack will be used when
869 where this pointer will be passed to other GDB stub functions.
875 will serve as the entry point to GDB stub main loop.
915 values will then be written to hardware registers before switching
921 a ``g``/``G`` packets which will be sent back to GDB. The format of
927 GDB, GDB will abort the debugging session.
950 with software breakpoint or trap instructions. GDB will then
962 GDB will then rely on software breakpoints.