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/26769] assert when comparing libstdc++ to itself
Date: Fri, 23 Oct 2020 22:22:13 +0000	[thread overview]
Message-ID: <bug-26769-9487-3c4v4J9AIO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26769-9487@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Ben Woodard <woodard at redhat dot com> ---
This problem continues to exist with the trunk version of libabigail 

The problem has a similar assert but the line number is slightly different.

abidiff: ../../../libabigail/src/abg-reader.cc:1287:
abigail::ir::type_base_sptr
abigail::xml_reader::read_context::build_or_get_type_decl(const string&, bool):
Assertion `__abg_cond__' failed.

All of these libraries from Fedora 33 exhibit this problem.

/lib64/libTKBO.so.7.4.0
/lib64/libTKIVtk.so.7.4.0
/lib64/libsource-highlight.so.4.0.1
/lib64/libTKSTEPBase.so.7.4.0
/lib64/libdnf.so.2
/lib64/libboost_python39.so.1.73.0
/lib64/libpoppler-cpp.so.0.9.0
/lib64/libpoppler-glib.so.8.18.0
/lib64/libTKSTEPAttr.so.7.4.0
/lib64/libTKMath.so.7.4.0
/lib64/libgeocoding.so.8.12
/lib64/libTKRWMesh.so.7.4.0
/lib64/libnumbertext-1.0.so.0.0.0
/lib64/libboost_regex.so.1.73.0
/lib64/librevenge-0.0.so.0.0.4
/lib64/libboost_serialization.so.1.73.0
/lib64/libboost_unit_test_framework.so.1.73.0
/lib64/libSoQt.so.1.6.0
/lib64/libgtkmm-3.0.so.1.1.0
/lib64/libTKMesh.so.7.4.0
/lib64/liborcus-0.15.so.0.0.0
/lib64/libcmis-0.5.so.5.0.0
/lib64/libclucene-core.so.2.3.3.4
/lib64/libboost_iostreams.so.1.73.0
/lib64/libQtCLucene.so.4.8.7
/lib64/libTKernel.so.7.4.0
/lib64/libTKSTEP209.so.7.4.0
/lib64/libpoppler.so.101.0.0
/lib64/libicutest.so.67.1
/lib64/libphonenumber.so.8.12
/lib64/libboost_wave.so.1.73.0
/lib64/libcmis-c-0.5.so.5.0.0
/lib64/libstdc++.so.6.0.28

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

  parent reply	other threads:[~2020-10-23 22:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22  5:10 [Bug default/26769] New: " woodard at redhat dot com
2020-10-22  6:00 ` [Bug default/26769] " woodard at redhat dot com
2020-10-23  4:48 ` woodard at redhat dot com
2020-10-23 22:22 ` woodard at redhat dot com [this message]
2020-11-10 10:22 ` dodji at redhat dot com
2020-11-12 22:23 ` woodard at redhat dot com
2020-11-16 17:15 ` dodji at redhat dot com
2020-11-16 20:33 ` woodard at redhat dot com
2020-11-17 17:39   ` Dodji Seketeli
2020-11-19 10:13   ` Dodji Seketeli
2020-11-17 17:39 ` dodji at seketeli dot org
2020-11-17 17:50 ` woodard at redhat dot com
2020-11-19 16:56 ` dodji at redhat dot com
2020-11-19 16:58 ` [Bug default/26769] abixml writer misses some member types in the output dodji at redhat dot com
2020-11-20 15:29 ` dodji at redhat dot com
2020-11-20 15:34 ` dodji at redhat dot com
2020-11-20 17:49 ` dodji at seketeli dot org
2020-11-20 22:29 ` woodard at redhat dot com
2020-11-23 12:26 ` dodji at redhat dot com
2020-11-23 17:42 ` woodard at redhat dot com
2020-11-24 10:39 ` 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-26769-9487-3c4v4J9AIO@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).