I have a process where one .o
file is built without any .eh_frame
or .debug_frame
section (via an assembler) but with other types of debug info such as .debug_info
. Apparently this triggers gdb to stop using frame-pointer (rbp
) based unwinding for any functions from that object, and it produces invalid backtraces (it isn't clear how it is trying to unwind the stack at all).
Now the functions in this binary set up the stack frame properly (i.e., rbp
points to correctly to the base of the frame) and if GDB were just to use that to unwind, everything would be great. Is there some way I can tell it to ignore the dwarf2
info and use frame-pointer based unwinding?