From: Simon Marchi <simark@simark.ca>
To: Jan Kratochvil <jan.kratochvil@redhat.com>,
Mitch Souders <mitch@runsafesecurity.com>
Cc: gdb@sourceware.org
Subject: Re: GDB reading eh_frame/eh_frame_hdr from disk
Date: Mon, 22 Jun 2020 14:17:47 -0400 [thread overview]
Message-ID: <05424d4d-eb4d-6214-6467-8ccf239a8731@simark.ca> (raw)
In-Reply-To: <20200622181453.GA3471048@host1.jankratochvil.net>
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?
Simon
next prev parent reply other threads:[~2020-06-22 18:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 22:37 Mitch Souders
2020-06-22 18:08 ` Simon Marchi
2020-06-22 18:16 ` Sterling Augustine
2020-06-22 18:14 ` Jan Kratochvil
2020-06-22 18:17 ` Simon Marchi [this message]
2020-06-22 18:20 ` Jan Kratochvil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=05424d4d-eb4d-6214-6467-8ccf239a8731@simark.ca \
--to=simark@simark.ca \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mitch@runsafesecurity.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).