public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/27267] Assertion comparing ABIs on rawhide
Date: Mon, 01 Feb 2021 13:49:15 +0000	[thread overview]
Message-ID: <bug-27267-9487-Xxo2zFQkRf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27267-9487@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27267

--- Comment #3 from dodji at redhat dot com ---
Hello,

So, I got the binaries attached and tried to reproduce the issue with the
libabigail 1.8.1 from Rawhide and Fedora 33 (they are the same code).  Here is
the output I am getting from Rawhide:

/usr/bin/abidiff
$ rpm -qf /usr/bin/abidiff
attention : Found bdb Packages database while attempting sqlite backend: using
bdb backend.
libabigail-1.8.1-1.fc34.x86_64
$ abidiff --version
abidiff: 1.8.1
$ abidiff --drop-private-types --fail-no-debug-info --no-added-syms 
libtotem-plparser.so.18.1.0 libtotem-plparser.so.18.3.4
Functions changes summary: 0 Removed, 1 Changed (8 filtered out), 0 Added (3
filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

1 function with some indirect sub-type change:

  [C] 'function void totem_pl_parser_add_ignored_mimetype(TotemPlParser*, const
char*)' at totem-pl-parser.c:2409:1 has some indirect sub-type changes:
    parameter 1 of type 'TotemPlParser*' has sub-type changes:
      in pointed to type 'typedef TotemPlParser' at totem-pl-parser.h:70:1:
        underlying type 'struct {GObject parent; TotemPlParserPrivate* priv;}'
at totem-pl-parser.h:67:1 changed: 
          type size hasn't changed
          1 data member change:
            type of 'TotemPlParserPrivate* priv' changed:
              in pointed to type 'typedef TotemPlParserPrivate' at
totem-pl-parser.h:60:1:
                underlying type 'struct TotemPlParserPrivate' at
totem-pl-parser.c:260:1 changed:
                  type size changed from 320 to 384 (in bits)
                  1 data member insertion:
                    'GHashTable* TotemPlParserPrivate::ignore_globs', at offset
128 (in bits) at totem-pl-parser.c:261:1
                  2 data member changes:
                    'GMutex TotemPlParserPrivate::ignore_mutex' offset changed
from 128 to 192 (in bits) (by +64 bits)
                    'GThread* TotemPlParserPrivate::main_thread' offset changed
from 192 to 256 (in bits) (by +64 bits)

$


So I don't seem to reproduce the issue with libabigail 1.8.1 that is in
currently in testing for Fedora 33.

Do you see the same?  Or am I missing something?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-02-01 13:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28 14:40 [Bug default/27267] New: " bugzilla at hadess dot net
2021-01-28 15:28 ` [Bug default/27267] " dodji at redhat dot com
2021-01-28 15:49 ` bugzilla at hadess dot net
2021-02-01 13:49 ` dodji at redhat dot com [this message]
2021-02-01 14:14 ` bugzilla at hadess dot net
2021-02-04 10:00 ` dodji at redhat dot com
2021-02-04 10:43 ` 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-27267-9487-Xxo2zFQkRf@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).