Re: GDB Frame Unwinding for Pure Assembly Code
Ahmad Nouralizadeh via Gdb <[email protected]>
| Newsgroups | gmane.comp.gdb.devel |
|---|---|
| Message-ID | <CAMYFX7nxegE8ZZKGT3JQMS3B7kxf9BErn+sWxYknkxpej-cvew@mail.gmail.com> |
Hi Jan, Thanks for the answer! Could you tell me why is an inline unwinder used? Regards. On Tuesday, 23 June 2020, Jan Kratochvil <[email protected]> wrote: > 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 > >