[Bug default/23641] confusion when a type definition DIE is matched by a supprspec and its decl DIEs aren't

["dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #4 from dodji at redhat dot com ---
"bochecha at daitauha dot fr" <sourceware-bugzilla@sourceware.org>
writes:

> Unfortunately, this doesn't seem to be entirely fixed. :-/

[...]

> But with abidiff from Git master, I get:
>
> $ ./tools/abidiff --no-added-syms --drop-private-types --headers-dir1
> $T1/usr/include --headers-dir2 $T2/usr/include --debug-info-dir1
> $T1/usr/lib/debug --debug-info-dir2 $T2/usr/lib/debug
> $T1/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2200.30
> $T2/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2400.0
> Functions changes summary: 0 Removed, 1 Changed (37 filtered out), 0 Added (31
> filtered out) functions
> Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
>
> 1 function with some indirect sub-type change:

[...]

Hmmh, I am afraid I couldn't reproduce by just recompiling Gtk 3.22.30
and Gtk 3.24 and running "make install".  It looks like something else
is happening when you are editing the binaries to split debug info
(maybe at debug info compression time?).  I'll have to get my hands on
you files libgtk-3.so.0.2200.30 libgtk-3.so.0.2400.0 as well as their
.debug corresponding files, so that I can inspect them.

For the record, here is what I am getting here:

$ ./build/tools/abidiff --no-added-syms --drop-private-types \
                        --hd1 ~/.local/gtk-3.22.30/usr/local/include \
                        --hd2 ~/.local/gtk-3.24.0/usr/local/include \
                       
~/.local/gtk-3.22.30/usr/local/lib/libgtk-3.so.0.2200.30 \
                        ~/.local/gtk-3.24.0/usr/local/lib/libgtk-3.so.0.2400.0

Functions changes summary: 0 Removed, 0 Changed, 0 Added (31 filtered out)
functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

$

In general, I think it's always better to attach the exact binaries you
are seeing issues on because there can be subtle variations in our
environments when I we to build the binaries on our respective systems.

Thanks.

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