GDB reading eh_frame/eh_frame_hdr from disk

Simon Marchi
Mon Jun 22 18:17:47 GMT 2020

On 2020-06-22 2:14 p.m., Jan Kratochvil via Gdb wrote:
> On Fri, 19 Jun 2020 00:37:42 +0200, Mitch Souders wrote:
>> Is there any way to tell gdb to use the in-memory representation from the
>> inferior of the .eh_frame/.eh_frame_hdr sections when doing stack
>> unwinding? As best I can determine, gdb always reaches out to disk to find
>> .eh_frame/.eh_frame_hdr to do stack unwinding. Our product is doing some
>> runtime manipulation of these sections and gdb's current behavior is
>> undesired.
> I am not aware GDB (nor LLDB) could do that. elfutils stack (eu-stack) can do
> that. One can test it by deleting the file on disk (such as during update of
> a running daemon) and backtrace it.

Ah, I guess it's because these sections are read by dwarf/read.c from the BFD
directly, these reads don't pass through target_ops?


More information about the Gdb mailing list