From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/28364] New: libwiretap fails self check with unspecified indirect sup-type changes
Date: Tue, 21 Sep 2021 20:11:30 +0000 [thread overview]
Message-ID: <bug-28364-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28364
Bug ID: 28364
Summary: libwiretap fails self check with unspecified indirect
sup-type changes
Product: libabigail
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: woodard at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
With trunk as of 1115e3f08e8f30e7e412294a563a78a15d0373c1
/usr/lib64/libwiretap.so.11.0.8 from wireshark-cli-3.4.8-1.fc34.x86_64 fails
consistency test.
/home/ben/Shared/Work/test/libabigail-x86_64/bin/abidw --abidiff
/usr/lib64/libwiretap.so.11.0.8
Functions changes summary: 0 Removed, 3 Changed, 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
3 functions with some indirect sub-type change:
[C] 'function void wtap_cleareof(wtap*)' at wtap.c:1421:1 has some indirect
sub-type changes:
[C] 'function void wtap_fdclose(wtap*)' at wtap.c:1386:1 has some indirect
sub-type changes:
[C] 'function void wtap_sequential_close(wtap*)' at wtap.c:1362:1 has some
indirect sub-type changes:
[Inferior 1 (process 1698173) exited with code 01]
Not a lot to go on with regards to what the indirect sub-type changes are.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-09-21 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 20:11 woodard at redhat dot com [this message]
2021-09-21 20:11 ` [Bug default/28364] " woodard at redhat dot com
2021-09-30 17:45 ` dodji at redhat dot com
2021-10-18 9:01 ` 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-28364-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).