public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@ecoscentric.com
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1002106] New: Bugs in vfscanf.cxx to deal with utf-8
Date: Fri, 20 Nov 2015 02:57:00 -0000 [thread overview]
Message-ID: <bug-1002106-13@http.bugs.ecos.sourceware.org/> (raw)
Please do not reply to this email, use the link below.
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1002106
Bug ID: 1002106
Summary: Bugs in vfscanf.cxx to deal with utf-8
Product: eCos
Version: 3.0
Target: All
Architecture/Host_ Other
OS:
Status: UNCONFIRMED
Severity: enhancement
Priority: low
Component: C library
Assignee: unassigned@bugs.ecos.sourceware.org
Reporter: 414256we@gmail.com
QA Contact: ecos-bugs@ecos.sourceware.org
CC: ecos-bugs@ecos.sourceware.org
Problem:
vfscanf have problem to deal with string in utf-8 format.
Analyze:
In function:
externC int
vfscanf (FILE *fp, const char *fmt0, va_list ap) __THROW {
u_char *fmt = (u_char *) fmt0;
It declared that:
char ccltab[256];
char curr_byte;
When a byte's highest bit(the sign bit) is set(e.g. 0xe5), doing the
following conversion:
(int)*CURR_POS
it surely will generates an integer that is larger than 256( Recall,
signed bit extension).
While try to combine it with:
ccltab[(int)*CURR_POS]
a fairly bug yields.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
next reply other threads:[~2015-11-20 2:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 2:57 bugzilla-daemon [this message]
2015-11-20 2:59 ` [Bug 1002106] " bugzilla-daemon
2015-11-20 8:19 ` bugzilla-daemon
2015-12-04 1:44 ` bugzilla-daemon
2015-11-20 2:57 [Bug 1002106] New: " bugzilla-daemon
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-1002106-13@http.bugs.ecos.sourceware.org/ \
--to=bugzilla-daemon@ecoscentric.com \
--cc=ecos-bugs@ecos.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).