From: "gprocida at google dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/28971] New: changes to symbols unreferenced by debug info are not reported
Date: Wed, 16 Mar 2022 14:22:50 +0000 [thread overview]
Message-ID: <bug-28971-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28971
Bug ID: 28971
Summary: changes to symbols unreferenced by debug info are not
reported
Product: libabigail
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: gprocida at google dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
Reporting of symbols unreferenced-by-debug-info appears to be restricted to the
reporting of addition/removal only. There is no code to enumerate such symbols
that have changed and then call maybe_report_diff_for_symbol (as far as I can
tell).
The function symbol exported_function_gpl in the existing test file
tests/data/test-abidiff/test-crc-{1,2}.xml has no associated declaration with
matching elf-symbol-id attribute.
All the exported_function_gpl symbol attributes are the same between the two
files and as expected there is no diff for the symbol in the corresponding
tests/data/test-abidiff/test-crc-report.txt.
However if the CRC attribute, for example, of exported_function_gpl is changed
in one of the files, no diff is still reported.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-03-16 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 14:22 gprocida at google dot com [this message]
2022-03-17 17:07 ` [Bug default/28971] " gprocida at google 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-28971-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).