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/29610] support reading an ocaml abixml symbol table table where a function symbol aliases a variable symbol
Date: Tue, 11 Oct 2022 20:19:47 +0000	[thread overview]
Message-ID: <bug-29610-9487-LTueRR5cth@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29610-9487@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Ben Woodard <woodard at redhat dot com> ---
With the latest trunk as of 4c5f44473e9f7c0a561174fdc6cc89f40dd9892a

The ocaml asserts continue to happen. It would be nice if instead of an assert,
it printed out some useful message or something.

In addition to affecting ocaml that assert:
../../../libabigail/src/abg-reader.cc:3400:
abigail::ir::string_elf_symbols_map_sptr
abigail::xml_reader::build_elf_symbol_db(read_context&, xmlNodePtr, bool):
Assertion `__abg_cond__' failed.

Also seems to affect the planets and why3 packages in Fedora 37

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

  reply	other threads:[~2022-10-11 20:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-25  3:59 [Bug default/29610] New: " dodji at redhat dot com
2022-10-11 20:19 ` woodard at redhat dot com [this message]
2023-01-07  0:43 ` [Bug default/29610] " woodard at redhat dot com
2023-03-24 17:41 ` dodji at redhat dot com
2023-03-27 19:13 ` woodard at redhat dot com
2023-04-11 14:44 ` dodji at redhat dot com
2023-04-11 14:46 ` dodji at redhat dot com
2023-04-11 14:49 ` dodji at redhat dot com
2023-04-11 15:41 ` dodji at redhat dot com
2024-04-04  9:35 ` dodji at seketeli dot org
2024-04-04 15:14 ` dodji at seketeli dot org

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-29610-9487-LTueRR5cth@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).