From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/27569] abidiff misses a function parameter addition
Date: Wed, 24 Mar 2021 17:10:41 +0000 [thread overview]
Message-ID: <bug-27569-9487-ED4aLGCnay@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27569-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27569
dodji at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2021-03-24
--- Comment #3 from dodji at redhat dot com ---
using --harmless gives a huge output, including the information about parameter
2 being being added.
Is it possible to have the two offending binaries?
When dealing with this type of issue, I'd rather work on binaries than abixml
as the issue might be in the process of emitting the abixml.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-24 17:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 15:21 [Bug default/27569] New: " gprocida+abigail at google dot com
2021-03-15 13:17 ` [Bug default/27569] " gprocida+abigail at google dot com
2021-03-15 13:24 ` gprocida+abigail at google dot com
2021-03-24 17:10 ` dodji at redhat dot com [this message]
2021-03-24 17:18 ` gprocida+abigail at google dot com
2021-03-24 23:58 ` gprocida+abigail at google dot com
2021-03-25 10:07 ` dodji at redhat dot com
2021-03-25 11:22 ` dodji at redhat dot com
2021-03-25 16:33 ` Giuliano Procida
2021-03-26 11:25 ` Dodji Seketeli
2021-03-25 16:34 ` gprocida at google dot com
2021-03-26 11:26 ` dodji at seketeli dot org
2021-03-29 17:55 ` 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-27569-9487-ED4aLGCnay@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).