From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29345] New: abipkgdiff --self-check can't read its own file for dx-4.4.4-58.fc36.armv7hl.rpm
Date: Sat, 09 Jul 2022 18:33:11 +0000 [thread overview]
Message-ID: <bug-29345-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29345
Bug ID: 29345
Summary: abipkgdiff --self-check can't read its own file for
dx-4.4.4-58.fc36.armv7hl.rpm
Product: libabigail
Version: unspecified
Status: NEW
Severity: minor
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: woodard at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
This one is not terribly important but it also looks like a trivial thing to
fix. For some reason, abipkgdiff seems to be truncating lines in its own abixml
file. The problem doesn't seem to happen on other architectures.
$ abipkgdiff --self-check --d1
/home/ben/.cache/fedabipkgdiff/downloads/dx-debuginfo-4.4.4-58.fc36.armv7hl.rpm
/home/ben/.cache/fedabipkgdiff/downloads/dx-4.4.4-58.fc36.armv7hl.rpm | less
/home/ben/.cache/libabigail/abipkgdiff-tmp-dir-0oaQpN/package1/abixml/usr/lib/dx/bin_linux/tutor.abi:1015:
parser error : error parsing attribute name
root' type-id='type-id-2' visibility='default' filepath='/usr/include/X11/Xlib'
^
/home/ben/.cache/libabigail/abipkgdiff-tmp-dir-0oaQpN/package1/abixml/usr/lib/dx/bin_linux/tutor.abi:1015:
parser error : attributes construct error
root' type-id='type-id-2' visibility='default' filepath='/usr/include/X11/Xlib'
^
/home/ben/.cache/libabigail/abipkgdiff-tmp-dir-0oaQpN/package1/abixml/usr/lib/dx/bin_linux/tutor.abi:1015:
parser error : error parsing attribute name
root' type-id='type-id-2' visibility='default' filepath='/usr/include/X11/Xlib'
^
/home/ben/.cache/libabigail/abipkgdiff-tmp-dir-0oaQpN/package1/abixml/usr/lib/dx/bin_linux/tutor.abi:1015:
parser error : attributes construct error
root' type-id='type-id-2' visibility='default' filepath='/usr/include/X11/Xlib'
^
/home/ben/.cache/libabigail/abipkgdiff-tmp-dir-0oaQpN/package1/abixml/usr/lib/dx/bin_linux/tutor.abi:1015:
parser error : Couldn't find end of Start Tag var-decl
root' type-id='type-id-2' visibility='default' filepath='/usr/include/X11/Xlib'
^
/home/ben/.cache/libabigail/abipkgdiff-tmp-dir-0oaQpN/package1/abixml/usr/lib/dx/bin_linux/tutor.abi:1015:
parser error : Couldn't find end of Start Tag var-decl
root' type-id='type-id-2' visibility='default' filepath='/usr/include/X11/Xlib'
^
abipkgdiff: ../../../libabigail/src/abg-reader.cc:1488:
abigail::ir::type_base_sptr
abigail::xml_reader::read_context::build_or_get_type_decl(const std::string&,
bool): Assertion `__abg_cond__' failed.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-07-09 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 18:33 woodard at redhat dot com [this message]
2022-07-26 18:48 ` [Bug default/29345] " woodard at redhat dot com
2022-07-26 18:49 ` woodard at redhat dot com
2022-07-28 18:52 ` woodard at redhat dot com
2022-10-14 18:52 ` woodard at redhat dot com
2023-03-23 22:58 ` woodard at redhat dot com
2023-03-26 22:10 ` [Bug default/29345] abipkgdiff is confused by symlinked binaries in RPMs dodji at redhat dot com
2023-03-26 23:17 ` 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-29345-9487@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).