From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/19434] invalid character in attribute value
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <bug-19434-9487-kODbKyjZ9j@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19434-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19434
dodji at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from dodji at redhat dot com ---
So this is due to some function parameter names which contain ASCII *control*
characters. I am not sure why this would happen. Maybe this is because the
source code file was encoded in something that is not proper ASCII?
Unfortunately, I am not aware of any way to detect the encoding of the source
file, from the DWARF information; so I am assuming it should be ASCII.
The fix involves detecting characters that are not simple ASCII identifier
characters in parameter names. If there is any, the parameter name is dropped
on the floor.
The fix has landed into the master branch at
https://sourceware.org/git/?p=libabigail.git;a=commit;h=c3869ecc7bbd6f8370ca29446afdcc1d2631e33d.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2016-01-18 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 [Bug default/19434] New: " woodard at redhat dot com
2016-01-01 0:00 ` [Bug default/19434] " woodard at redhat dot com
2016-01-01 0:00 ` Dodji Seketeli
2016-01-01 0:00 ` dodji at redhat dot com
2016-01-01 0:00 ` woodard at redhat dot com
2016-01-01 0:00 ` dodji at seketeli dot org
2016-01-01 0:00 ` woodard at redhat dot com
2016-01-01 0:00 ` dodji at redhat dot com [this message]
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-19434-9487-kODbKyjZ9j@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).