From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29553] New: libabigail potentially misses some function declarations
Date: Tue, 06 Sep 2022 16:26:09 +0000 [thread overview]
Message-ID: <bug-29553-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29553
Bug ID: 29553
Summary: libabigail potentially misses some function
declarations
Product: libabigail
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: dodji at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
The problem can be reproduced from a tarball accessible from
https://usercontent.irccloud-cdn.com/file/XEp8xIow/test_c.tar.gz.
Here is the bug report I got from our IRC channel:
<vvvvvv> Hi, Dodji! I stumbled upon a bug in libabigail, relative to
`build_function_decl` in abg-dwarf-reader.cc. Looks like it skips all
references from function declaration, if it was previously seen in other CU,
which may lead to missing declaration for some classes. I've made an example
with two CU and Makefile, you could build it using regular `make` and run
something like `abidw --type-id-style hash --no-comp-dir-path
[18:03]
<vvvvvv> --no-show-locs --no-linux-kernel-mode test.so`. And in output you
could see missing declaration for `struct Common`, but it exists in DWARF,
which could be seen by running `llvm-dwarfdump test.so`. Moreover, if you swap
`user.o` and `test.o` in `Makefile`
<vvvvvv> https://usercontent.irccloud-cdn.com/file/XEp8xIow/test_c.tar.gz
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2022-09-06 16:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-29553-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).