From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/28761] New: libdovecot-storage.so.0.0.0 fails self-test
Date: Tue, 11 Jan 2022 02:00:40 +0000 [thread overview]
Message-ID: <bug-28761-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28761
Bug ID: 28761
Summary: libdovecot-storage.so.0.0.0 fails self-test
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 the latest trunk as of 71633a7c0c7c96c03db8c18826afea26da0f7b4b:
libdovecot-storage.so.0.0.0 from dovecot-2.3.17.1-1.fc35.x86_64 fails a
selftest:
$ abidw --abidiff /usr/lib64/dovecot/libdovecot-storage.so.0.0.0
Functions changes summary: 0 Removed, 4 Changed, 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
4 functions with some indirect sub-type change:
[C] 'function void mbox_dotlock_touch(mbox_mailbox*)' at mbox-lock.c:889:1
has some indirect sub-type changes:
parameter 1 of type 'mbox_mailbox*' has sub-type changes:
in pointed to type 'struct mbox_mailbox' at mbox-storage.h:40:1:
type size hasn't changed
1 data member change:
type of 'mbox_storage* storage' changed:
in pointed to type 'struct mbox_storage' at mbox-storage.h:31:1:
type size hasn't changed
2 data member changes:
type of 'mbox_lock_type* read_locks' changed:
in pointed to type 'enum mbox_lock_type':
enum type enum mbox_lock_type was a defined enum type and
is now a declaration-only enum type
type of 'mbox_lock_type* write_locks' changed:
in pointed to type 'enum mbox_lock_type':
enum type enum mbox_lock_type was a defined enum type and
is now a declaration-only enum type
[C] 'function unsigned int mbox_get_cur_lock_id(mbox_mailbox*)' at
mbox-lock.c:883:1 has some indirect sub-type changes:
parameter 1 of type 'mbox_mailbox*' has sub-type changes:
pointed to type 'struct mbox_mailbox' changed at mbox-storage.h:40:1, as
reported earlier
[C] 'function int mbox_lock(mbox_mailbox*, int, unsigned int*)' at
mbox-lock.c:777:1 has some indirect sub-type changes:
parameter 1 of type 'mbox_mailbox*' has sub-type changes:
pointed to type 'struct mbox_mailbox' changed at mbox-storage.h:40:1, as
reported earlier
[C] 'function int mbox_unlock(mbox_mailbox*, unsigned int)' at
mbox-lock.c:840:1 has some indirect sub-type changes:
parameter 1 of type 'mbox_mailbox*' has sub-type changes:
pointed to type 'struct mbox_mailbox' changed at mbox-storage.h:40:1, as
reported earlier
[Inferior 1 (process 155320) exited with code 01]
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-01-11 2:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 2:00 woodard at redhat dot com [this message]
2022-01-11 2:00 ` [Bug default/28761] " woodard at redhat dot com
2022-06-29 18:47 ` woodard at redhat dot com
2022-06-29 20:44 ` woodard at redhat dot com
2022-06-29 20:45 ` woodard at redhat dot com
2022-07-04 12:59 ` dodji at redhat dot com
2022-07-07 15:51 ` woodard 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-28761-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).