From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/26769] assert when comparing libstdc++ to itself
Date: Thu, 19 Nov 2020 16:56:58 +0000 [thread overview]
Message-ID: <bug-26769-9487-t7pClmi4R7@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 #9 from dodji at redhat dot com ---
(In reply to Ben Woodard from comment #6)
> This latest patch 9ab30d86bd853b4561a9490898b65fc1fd5a203e seems to have
> greatly improved the situation. I'm down to 56 failures rather than over
> 300. However the majority of the remaining problems still seem to hit this
> problem just in a different way. 51/56 of the remaining failures look like
> this:
>
> $ cat libabigail.so.0.0.0.bt
> Reading symbols from abidw...
> Starting program: /home/ben/Scratch/Work/test/libabigail-x86_64/bin/abidw
> --abidiff /lib64/libabigail.so.0.0.0
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> abidw: ../../../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.
>
> Program received signal SIGABRT, Aborted.
Okay, I have updated the content of branch
https://sourceware.org/git/?p=libabigail.git;a=shortlog;h=refs/heads/dodji/PR26769.
The current commit hash is d35b656da75130. You can browse it at
https://sourceware.org/git/?p=libabigail.git;a=commit;h=d35b656da75130bd976049001247742a49127e0c.
This should hopefully fix the remaining issue that you are pointing to here.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-11-19 16:56 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
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 [this message]
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-t7pClmi4R7@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).