From: Giuliano Procida <gprocida@google.com>
To: Mark Wielaard <mark@klomp.org>
Cc: "Giuliano Procida via Libabigail" <libabigail@sourceware.org>,
"Dodji Seketeli" <dodji@seketeli.org>,
kernel-team@android.com, "Matthias Männich" <maennich@google.com>
Subject: Re: [PATCH] DWARF reader: Comment ARM32 ELF address interpretation
Date: Fri, 12 Mar 2021 09:39:21 +0000 [thread overview]
Message-ID: <CAGvU0HnnH00Z=Q4JL6bjYjw+qxW6e4LXNtVUcVpqvjceLBOGQg@mail.gmail.com> (raw)
In-Reply-To: <6fb8e0f870686efc61715588510cccb70aa05eff.camel@klomp.org>
Hi.
On Thu, 11 Mar 2021 at 17:16, Mark Wielaard <mark@klomp.org> wrote:
> Hi,
>
> On Wed, 2021-03-10 at 12:22 +0000, Giuliano Procida wrote:
> > Bug 27552 - libabigail needs to interpret ARM32 symbol addresses
> > specially
>
> BTW. I tried to get this correct for elfutils when using the libdwfl
> dwfl_module_addrsym and dwfl_module_addrinfo functions:
> https://sourceware.org/bugzilla/show_bug.cgi?id=27564
> Has a proposed patch that needs a bit more testing (and maybe a tweak).
>
>
Having a library layer that does all the fixups seems a lot better than
having the logic in libabigail.
> libabigail doesn't use these functions, but one benefit of them is that
> they also handle the case of ppc function descriptors (that is old
> style ppc32 and ppc64be).
>
>
Hopefully, they are relatively straightforward to drop in. However,
Matthias has symbol table reader changes still queued up; once these are
done, we can take a look.
libabibgail would become dependent on libdwfl version >= X for correctness,
so we'd need to assert that at compile time.
Thanks,
Giuliano.
> Cheers,
>
> Mark
>
prev parent reply other threads:[~2021-03-12 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 12:22 Giuliano Procida
2021-03-11 9:11 ` Dodji Seketeli
2021-03-11 17:16 ` Mark Wielaard
2021-03-12 9:39 ` Giuliano Procida [this message]
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='CAGvU0HnnH00Z=Q4JL6bjYjw+qxW6e4LXNtVUcVpqvjceLBOGQg@mail.gmail.com' \
--to=gprocida@google.com \
--cc=dodji@seketeli.org \
--cc=kernel-team@android.com \
--cc=libabigail@sourceware.org \
--cc=maennich@google.com \
--cc=mark@klomp.org \
/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).