From: "sourceware at rahix dot de" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/26146] New: No type information for ARM thumb object files
Date: Sun, 21 Jun 2020 11:36:24 +0000 [thread overview]
Message-ID: <bug-26146-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26146
Bug ID: 26146
Summary: No type information for ARM thumb object files
Product: libabigail
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: sourceware at rahix dot de
CC: libabigail at sourceware dot org
Target Milestone: ---
Created attachment 12630
--> https://sourceware.org/bugzilla/attachment.cgi?id=12630&action=edit
ARM thumb object file for reproduction
It looks like libabigail fails to extract type information from ARM thumb
object files.
Compiling a test file using 'arm-none-eabi-gcc -g' produces an object file
that libabigail can extract type information from, but 'arm-none-eabi-gcc
-g -mthumb' does not. The object file does contain debug symbols as I can
see with `eu-readelf --debug-dump=info`.
Using `abidw` I just get this:
<abi-corpus path='thumb.o' architecture='elf-arm'>
<elf-function-symbols>
<!-- func_a -->
<elf-symbol name='func_a' type='func-type' binding='global-binding'
visibility='default-visibility' is-defined='yes'/>
<!-- func_b -->
<elf-symbol name='func_b' type='func-type' binding='global-binding'
visibility='default-visibility' is-defined='yes'/>
</elf-function-symbols>
</abi-corpus>
The source for the test file was:
int func_a(char *buf, unsigned char len)
{
return -1;
}
char *func_b(char *ptr, void *ptr2)
{
return NULL;
}
I've attached the object file.
Regards,
Rahix
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-06-21 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 11:36 sourceware at rahix dot de [this message]
2021-04-23 7:31 ` [Bug default/26146] " gprocida+abigail at google dot com
2021-04-23 15:40 ` sourceware at rahix dot de
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-26146-9487@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).