From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/27727] New: /usr/lib64/libgdal.so.28.0.2 fails self check
Date: Tue, 13 Apr 2021 20:11:40 +0000 [thread overview]
Message-ID: <bug-27727-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27727
Bug ID: 27727
Summary: /usr/lib64/libgdal.so.28.0.2 fails self check
Product: libabigail
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: woodard at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
With trunk as of b215a2115376225b04b4d6b25acc6c5a1b4021e9 the self check of
/usr/lib64/libgdal.so.28.0.2 from gdal-libs-3.2.2-1.fc34.x86_64 fails
This one is one that I have never seen before. It appears like the file is
getting written incorrectly.
$ /home/ben/Shared/Work/test/libabigail-x86_64/bin/abidw --abidiff
/usr/lib64/libgdal.so.28.0.2
/tmp/libabigail-tmp-file-Msp0O0:529896: parser error : Unescaped '<' not
allowed in attributes values
<enum-decl name='__anonymous_enum__' is-anonymous='yes'
linkage-name='<ano
^
/tmp/libabigail-tmp-file-Msp0O0:529896: parser error : attributes construct
error
<enum-decl name='__anonymous_enum__' is-anonymous='yes'
linkage-name='<ano
^
/tmp/libabigail-tmp-file-Msp0O0:529896: parser error : Couldn't find end of
Start Tag enum-decl
<enum-decl name='__anonymous_enum__' is-anonymous='yes'
linkage-name='<ano
^
/home/ben/Shared/Work/test/libabigail-x86_64/bin/abidw: Could not read
temporary XML representation of elf file back
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-04-13 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 20:11 woodard at redhat dot com [this message]
2021-04-13 20:11 ` [Bug default/27727] " woodard at redhat dot com
2021-06-08 22:09 ` woodard at redhat dot com
2021-09-07 17:22 ` woodard at redhat dot com
2021-09-08 15:04 ` 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-27727-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).