From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/27552] libandroid.so missing symbol type information
Date: Tue, 09 Mar 2021 21:49:02 +0000 [thread overview]
Message-ID: <bug-27552-9487-BNeARuUiBK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27552-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27552
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
So this is ./tests/data/test-read-dwarf/test-libandroid.so
Which is a 32bit ARM binary.
Those are "special" :)
https://static.docs.arm.com/ihi0044/g/aaelf32.pdf
Section 5.5.3 Symbol Values
• If the symbol addresses a Thumb instruction, its value is the address of the
instruction with bit zero set (in a relocatable object, the section offset with
bit zero set).
This allows a linker to distinguish Arm and Thumb code symbols without having
to refer to the map. An Arm symbol will always have an even value, while a
Thumb symbol will always have an odd value.
So it depends on when which tool strips off the zero-bit of the value.
It looks like AAssetDir_close is a Thumb function, so its address is 0000ce62,
but the value in the symbol table is 0000ce63.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-09 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 16:20 [Bug default/27552] New: " gprocida+abigail at google dot com
2021-03-09 20:21 ` [Bug default/27552] " gprocida+abigail at google dot com
2021-03-09 21:49 ` mark at klomp dot org [this message]
2021-03-09 22:29 ` [Bug default/27552] libabigail needs to interpret ARM32 symbol addresses specially gprocida+abigail at google dot com
2021-03-22 17:42 ` dodji at redhat dot com
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=bug-27552-9487-BNeARuUiBK@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@sourceware.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).