Lines Matching refs:be

12 that stack traces can be reliable.
36    code and debug tools to be able to walk the stack to determine the
41    CONFIG_FRAME_POINTER.  For some other architectures they may be
47    But for asm code, the frame setup instructions have to be written by
51    For stack traces based on frame pointers to be reliable, all
55    of the first function will be skipped on the stack trace.
89    functions honor CONFIG_FRAME_POINTER, no functions will ever[*] be
99    An alternative to frame pointers and DWARF, ORC unwind data can be
101    band.  So it doesn't affect runtime performance and it can be
110    stack traces need to be reliable (or an unreliable condition needs to
111    be detectable).  Objtool makes that possible.
121 1. Each callable function must be annotated as such with the ELF
125    callable code which should be annotated accordingly.
131    be annotated as an ELF function.  The ENDPROC macro shouldn't be used
144    function B, the _caller_ of function A will be skipped on the stack
161    which shouldn't be be in callable functions anyway.
194    If it's a GCC-compiled .c file, the error may be because the function
210    reachable from) a callable function, the function should be annotated
212    Otherwise, the code should probably be annotated with the unwind hint
238    the callable function annotation (ENDPROC) and should always be
277    can fall through into the next function.  There could be different
281       panic().  In this case the noreturn function needs to be added to
289       might be corrupt due to a gcc bug.  For more details, see:
301 If the error doesn't seem to make sense, it could be a bug in objtool.