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/27327] types seem to get confused in libjavascriptcoregtk-4.0.so.18.17.12
Date: Wed, 03 Feb 2021 03:52:27 +0000	[thread overview]
Message-ID: <bug-27327-9487-jdFfahf6ga@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27327-9487@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Ben Woodard <woodard at redhat dot com> ---
It may be that the thing that is going wrong is earlier where the ELF symbols
are being aliased. There is another thing that my testing kicks out which is
somewhat similar:

/home/ben/Shared/Work/test/libabigail-x86_64/bin/abidw --abidiff
/lib64/libstdc++.so.6.0.28
Download failed: File exists.  Continuing without debug info for
/home/ben/Shared/test/system-supplied DSO at 0x7ffff7fcf000.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Functions changes summary: 0 Removed, 1 Changed, 0 Added function
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

1 function with some indirect sub-type change:

  [C] 'method virtual int std::codecvt<char16_t, char,
__mbstate_t>::do_max_length() const' at codecvt.h:573:1 has some indirect
sub-type changes:
    Please note that the symbol of this function is
_ZNKSt7codecvtIDic11__mbstate_tE13do_max_lengthEv@@GLIBCXX_3.4.21
     and it aliases symbols:
_ZNKSt7codecvtIDsDu11__mbstate_tE13do_max_lengthEv@@GLIBCXX_3.4.26,
_ZNKSt7codecvtIDsc11__mbstate_tE13do_max_lengthEv@@GLIBCXX_3.4.21,
_ZNKSt7codecvtIDiDu11__mbstate_tE13do_max_lengthEv@@GLIBCXX_3.4.26
    'method virtual int std::codecvt<char16_t, char,
__mbstate_t>::do_max_length() const
{_ZNKSt7codecvtIDic11__mbstate_tE13do_max_lengthEv@@GLIBCXX_3.4.21,
_ZNKSt7codecvtIDsDu11__mbstate_tE13do_max_lengthEv@@GLIBCXX_3.4.26,
_ZNKSt7codecvtIDsc11__mbstate_tE13do_max_lengthEv@@GLIBCXX_3.4.21,
_ZNKSt7codecvtIDiDu11__mbstate_tE13do_max_lengthEv@@GLIBCXX_3.4.26}' now
becomes 'method virtual int std::codecvt<char32_t, char,
__mbstate_t>::do_max_length() const
{_ZNKSt7codecvtIDic11__mbstate_tE13do_max_lengthEv@@GLIBCXX_3.4.21,
_ZNKSt7codecvtIDsDu11__mbstate_tE13do_max_lengthEv@@GLIBCXX_3.4.26,
_ZNKSt7codecvtIDsc11__mbstate_tE13do_max_lengthEv@@GLIBCXX_3.4.21,
_ZNKSt7codecvtIDiDu11__mbstate_tE13do_max_lengthEv@@GLIBCXX_3.4.26}'
    implicit parameter 0 of type 'const std::codecvt<char16_t, char,
__mbstate_t>*' changed:
      in pointed to type 'const std::codecvt<char16_t, char, __mbstate_t>':
        'const std::codecvt<char16_t, char, __mbstate_t>' changed to 'const
std::codecvt<char32_t, char, __mbstate_t>'

[Inferior 1 (process 603341) exited with code 01]

There it is swapping a 32b function and a 16b function.

that was with libstdc++-10.2.1-9.fc33.x86_64 /lib64/libstdc++.so.6.0.28

Might be the same bug might be different hard to say but in this case I think
that they are the same.

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

  parent reply	other threads:[~2021-02-03  3:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03  3:43 [Bug default/27327] New: " woodard at redhat dot com
2021-02-03  3:44 ` [Bug default/27327] " woodard at redhat dot com
2021-02-03  3:52 ` woodard at redhat dot com [this message]
2021-03-04 20:15 ` woodard at redhat dot com
2021-03-04 21:41 ` 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-27327-9487-jdFfahf6ga@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).