Lines Matching refs:unwind
46 the stack or other unwind state is corrupt or otherwise unreliable. The
63 In some cases, an unwinder may require metadata to correctly unwind.
82 * Missing unwind support for an uncommon scenario, or a bug in the unwinder.
117 which is known to be reliable to unwind from, and reject unwinding from all
125 unreliable to unwind from, e.g.
135 At function call boundaries the stack and other unwind state is expected to be
143 If an interrupt or other exception is taken while the stack or other unwind
144 state is in an inconsistent state, it may not be possible to reliably unwind,
148 Architectures which cannot identify when it is reliable to unwind such cases
150 boundaries. Note that it may be reliable to unwind across certain
151 exceptions (e.g. IRQ) but unreliable to unwind across other exceptions
154 Architectures which can identify when it is reliable to unwind such cases (or
155 have no such cases) should attempt to unwind across exception boundaries, as
173 unwinder can reliably determine the original return address and no unwind state
215 Architectures might not always be able to unwind such sequences, such as when
219 It is recommended that architectures unwind cases where return_to_handler has
220 not yet been returned to, but architectures are not required to unwind from the
222 are not required to unwind from other trampolines which modify the return
229 returns, but do transiently clobber the return address or other unwind state.
249 Architectures must either ensure that unwinders either reliably unwind