GDB Frame Unwinding for Pure Assembly Code

Jan Kratochvil jan.kratochvil@redhat.com
Tue Jun 23 07:26:54 GMT 2020


On Mon, 22 Jun 2020 23:55:30 +0200, Ahmad Nouralizadeh via Gdb wrote:
> But knowing the GDB mechanism to get over the problem will be helpful.

GDB disassembles the code and tries to guess how to unwind it.
amd64-tdep.c amd64_analyze_prologue(), amd64_frame_cache_1() etc.

That is just a last resort way of unwinding (=a bug in the debuggee), there
should always be .eh_frame in the debuggee, also for throwing exceptions
across such .eh_frame-less functions if there is any callback there.


Jan



More information about the Gdb mailing list