Lines Matching refs:frame
22 alternative to frame pointer based unwinding
115 validates the correct frame pointer state at each instruction.
125 a) More reliable stack traces for frame pointer enabled kernels
132 For some architectures, frame pointers are enabled by
137 frame pointers when the -fno-omit-frame-pointer option is used.
139 But for asm code, the frame setup instructions have to be written by
143 For stack traces based on frame pointers to be reliable, all
144 functions which call other functions must first create a stack frame
145 and update the frame pointer. If a first function doesn't properly
146 create a stack frame before calling a second function, the *caller*
149 For example, consider the following example backtrace with frame
164 If we remove the frame pointer logic from cmdline_proc_show() by
165 replacing the frame pointer related instructions with nops, here's
185 beginning of a function before the stack frame has been created,
186 or at the very end of the function after the stack frame has been
187 destroyed. This is an inherent limitation of frame pointers.
191 An alternative to frame pointers and DWARF, ORC unwind data can be
192 used to walk the stack. Unlike frame pointers, ORC data is out of
225 correct frame pointer logic, if required by CONFIG_FRAME_POINTER or
229 This rule ensures that frame pointer based stack traces will work as
230 designed. If function A doesn't create a stack frame before calling
238 b) the jump matches sibling call semantics and the frame pointer has
269 -fno-omit-frame-pointer or adds -fomit-frame-pointer to the gcc options.
276 1. file.o: warning: objtool: func()+0x128: call without frame pointer save/setup
279 updating the frame pointer, and CONFIG_FRAME_POINTER is enabled.
282 function, add proper frame pointer logic using the FRAME_BEGIN and
295 Otherwise the stack frame may not get created before the call.
301 …arch/x86/kvm/kvm.o: warning: objtool: .altinstr_replacement+0xc5: call without frame pointer save/…
358 ….o: warning: objtool: func()+0x26: sibling call from callable instruction with modified stack frame
373 The instruction's frame pointer state is inconsistent, depending on
377 pushes and sets up the frame pointer (for x86_64, this means rbp) at
379 Also make sure that no other code in the function touches the frame
383 does some unusual things to the stack or the frame pointer. In such