Lines Matching +full:use +full:- +full:cases

16 to identify which functions are live is to use a stacktrace.
19 functions with live state, and best-effort approaches which can be helpful for
38 * The return code is non-zero to indicate that the trace is not reliable.
41    In some cases it is legitimate to omit specific functions from the trace,
42    but all other functions must be reported. These cases are described in
45 Secondly, the reliable stacktrace function must be robust to cases where
47 function should attempt to detect such cases and return a non-zero error
49 an unsafe way.  Specific cases are described in further detail below.
52 3. Compile-time analysis
55 To ensure that kernel code can be correctly unwound in all cases,
59 functions use specific prologue and epilogue sequences. Architectures
63 In some cases, an unwinder may require metadata to correctly unwind.
76 --------------------------------------
99 -------------------------------
115 To ensure that such cases do not result in functions being omitted from a
133 ----------------------------------------------
137 case part-way through a function. For example, during a function prologue or
148 Architectures which cannot identify when it is reliable to unwind such cases
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
160 ---------------------------------
176 unwinder must report these cases as unreliable.
183 .. code-block:: none
219 It is recommended that architectures unwind cases where return_to_handler has
226 ---------------------------------
239 .. code-block:: none
250 such cases, or report the unwinding as unreliable.
253 -------------------------------
266 .. code-block:: none
269            STP X29, X30, [SP, -16]!
291 .. code-block:: none
294            STP X29, X30, [SP, -16]!
305 Due to cases such as the above, it may only be possible to reliably consume a