From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/27518] abidw aborts during self check of /usr/lib64/libvte-2.91.so.0.6200.3
Date: Tue, 08 Jun 2021 22:04:23 +0000 [thread overview]
Message-ID: <bug-27518-9487-NTsuDZzew2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27518-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27518
--- Comment #2 from Ben Woodard <woodard at redhat dot com> ---
This no longer aborts. So that problem is resolved with the current libabigail
trunk. great! However, with the current version of libvte there are a bunch of
unspecified return type changes. I mentioned this in:
https://sourceware.org/bugzilla/show_bug.cgi?id=27969 where the current problem
may be a manifestation of a different problem. Or it may be non-crashing
continuation of this problem.
$ abidiff --harmless /usr/lib64/libvte-2.91.so.0.6400.1 libvte.abixml
Functions changes summary: 0 Removed, 12 Changed, 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
12 functions with some indirect sub-type change:
[C] 'function GType vte_cursor_blink_mode_get_type()' at
vtetypebuiltins.cc:7:1 has some indirect sub-type changes:
return type changed:
[C] 'function GType vte_cursor_shape_get_type()' at vtetypebuiltins.cc:27:1
has some indirect sub-type changes:
return type changed:
[C] 'function GType vte_erase_binding_get_type()' at vtetypebuiltins.cc:68:1
has some indirect sub-type changes:
return type changed:
[C] 'function GType vte_format_get_type()' at vtetypebuiltins.cc:171:1 has
some indirect sub-type changes:
return type changed:
[C] 'function GType vte_pty_error_get_type()' at vtetypebuiltins.cc:90:1 has
some indirect sub-type changes:
return type changed:
[C] 'function GType vte_pty_flags_get_type()' at vtetypebuiltins.cc:109:1 has
some indirect sub-type changes:
return type changed:
[C] 'function GType vte_pty_get_type()' at vtepty.cc:338:1 has some indirect
sub-type changes:
return type changed:
[C] 'function GType vte_regex_error_get_type()' at vtetypebuiltins.cc:152:1
has some indirect sub-type changes:
return type changed:
[C] 'function GType vte_regex_get_type()' at vteregex.cc:46:1 has some
indirect sub-type changes:
return type changed:
[C] 'function GType vte_terminal_get_type()' at vtegtk.cc:129:1 has some
indirect sub-type changes:
return type changed:
[C] 'function GType vte_text_blink_mode_get_type()' at
vtetypebuiltins.cc:47:1 has some indirect sub-type changes:
return type changed:
[C] 'function GType vte_write_flags_get_type()' at vtetypebuiltins.cc:134:1
has some indirect sub-type changes:
return type changed:
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-06-08 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 22:18 [Bug default/27518] New: " woodard at redhat dot com
2021-03-04 22:18 ` [Bug default/27518] " woodard at redhat dot com
2021-04-13 21:31 ` woodard at redhat dot com
2021-06-08 22:04 ` woodard at redhat dot com [this message]
2021-09-07 18:06 ` 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-27518-9487-NTsuDZzew2@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).