public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30307] arch specific self compare problem with bpftrace
Date: Mon, 03 Apr 2023 17:42:41 +0000	[thread overview]
Message-ID: <bug-30307-9487-lR8Ja5enm7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30307-9487@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Ben Woodard <woodard at redhat dot com> ---
The problem seeems to be some confustion between a pointer with a typedef'd
type vs the underlying structure.

$ abipkgdiff --self-check  --harmless --d1
/home/ben/.cache/fedabipkgdiff/downloads/darktable-tools-noise-debuginfo-4.2.1-1.fc37.x86_64.rpm
 --d1
/home/ben/.cache/fedabipkgdiff/downloads/darktable-debuginfo-4.2.1-1.fc37.x86_64.rpm
/home/ben/.cache/fedabipkgdiff/downloads/darktable-4.2.1-1.fc37.x86_64.rpm 

======== comparing'libdarktable.so' to itself wrongly yielded result:
===========
  Functions changes summary: 0 Removed, 88 Changed, 0 Added functions
  Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

  88 functions with some indirect sub-type change:

    [C] 'function void _dev_add_history_item(dt_develop_t*, dt_iop_module_t*,
gboolean, gboolean)' at develop.c:990:1 has some indirect sub-type changes:
      parameter 1 of type 'dt_develop_t*' has sub-type changes:
        in pointed to type 'typedef dt_develop_t' at develop.h:336:1:
          underlying type 'struct dt_develop_t' at develop.h:149:1 changed:
            type size hasn't changed
            3 data member changes:
              type of 'dt_iop_module_t* gui_module' changed:
                in pointed to type 'struct dt_iop_module_t' at imageop.h:183:1:
                  type size hasn't changed
                  52 data member changes:
                    type of 'void (dt_iop_module_so_t*)* init_presets' changed:
                      in pointed to type 'function type void
(dt_iop_module_so_t*)':
                        parameter 1 of type 'dt_iop_module_so_t*' has sub-type
changes:
                          in pointed to type 'struct dt_iop_module_so_t' at
imageop.h:155:1:
                            type size hasn't changed
                            49 data member changes:
                              type of 'void (dt_iop_module_so_t*)*
init_presets' changed:
                                in pointed to type 'function type void
(dt_iop_module_so_t*)':
                                  parameter 1 of type 'dt_iop_module_so_t*' has
sub-type changes:
                                    pointed to type 'struct dt_iop_module_so_t'
changed, as being reported
<snip>

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

  parent reply	other threads:[~2023-04-03 17:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 17:28 [Bug default/30307] New: " woodard at redhat dot com
2023-04-03 17:30 ` [Bug default/30307] " woodard at redhat dot com
2023-04-03 17:35 ` woodard at redhat dot com
2023-04-03 17:42 ` woodard at redhat dot com [this message]
2023-04-03 17:48 ` [Bug default/30307] " woodard at redhat dot com
2023-04-03 22:10 ` woodard at redhat dot com
2023-04-26 12:38 ` 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-30307-9487-lR8Ja5enm7@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).