From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/22429] Running abipkgdiff on firefox package aborts with message "in compare_dies at: abg-dwarf-reader.cc:11423: execution should not have reached this point!"
Date: Sun, 01 Jan 2017 00:00:00 -0000 [thread overview]
Message-ID: <bug-22429-9487-6JIrDfmvjC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22429-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22429
--- Comment #2 from dodji at redhat dot com ---
Okay, this is due to what seems to be an invalid debug info. That is, the
libxul.so file has invalid debug info.
Typically, there are references to type DIEs that are not defined in the debug
info. Typically, look at DIE number "[2cb2067a]". It describes a function
parameter. The type of that parameter is described by DIE [2ce6e18a]. But
then the definition of that that latter DIE can not be found in the debug info:
$ grep -A 5 2cb2067a extracts/usr/lib64/firefox/libxul.so.dwarf
[2cb2067a] formal_parameter
name (strp) "self"
decl_file (data1) 160
decl_line (data1) 1
type (ref4) [2ce6e18a]
[2cb20685] formal_parameter
dodji@adjoa:PR22429$ grep -A 5 2ce6e18a
extracts/usr/lib64/firefox/libxul.so.dwarf
type (ref4) [2ce6e18a]
[2cb20644] formal_parameter
name (strp) "raw_cap"
decl_file (data1) 160
decl_line (data1) 1
type (ref_addr) [2b9818d3]
--
type (ref4) [2ce6e18a]
[2cb2065c] variable
name (strp) "raw_cap"
alignment (udata) 1
decl_file (data1) 160
decl_line (data1) 62
--
type (ref4) [2ce6e18a]
[2cb20685] formal_parameter
name (strp) "len"
decl_file (data1) 160
decl_line (data1) 1
type (ref_addr) [2b9818d3]
--
type (ref4) [2ce6e18a]
[2cb2069d] variable
name (strp) "len"
alignment (udata) 1
decl_file (data1) 160
decl_line (data1) 45
$
So, this seems to be an invalid debug info generated by the Rust compiler.
There is an upstream bug file for it at
https://bugs.llvm.org/show_bug.cgi?id=35212.
Then, there is already a patch for that issue at
https://reviews.llvm.org/D39981.
So hopefully, this should be resolved soon, once the firefox build in Fedora is
updated.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-11-17 13:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 0:00 [Bug default/22429] New: " sinny at redhat dot com
2017-01-01 0:00 ` dodji at redhat dot com [this message]
2017-01-01 0:00 ` [Bug default/22429] " dodji at redhat dot com
2020-11-12 23:19 ` woodard at redhat dot com
2020-11-21 0:43 ` woodard at redhat dot com
2020-11-21 0:44 ` woodard at redhat dot com
2020-11-25 1:00 ` woodard at redhat dot com
2020-12-01 0:41 ` woodard at redhat dot com
2020-12-04 4:25 ` woodard at redhat dot com
2020-12-04 18:47 ` woodard at redhat dot com
2021-06-08 21:05 ` 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-22429-9487-6JIrDfmvjC@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).