public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@ecoscentric.com
To: unassigned@bugs.ecos.sourceware.org
Subject: [Bug 1002110] New: vfscanf does not support "hh" conversion
Date: Fri, 04 Dec 2015 01:41:00 -0000 [thread overview]
Message-ID: <bug-1002110-777@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=1002110
Bug ID: 1002110
Summary: vfscanf does not support "hh" conversion
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
While the standard said:
h Indicates that the conversion will be one of d, i, o, u, x, X, or n and
the next pointer is a pointer to a short int or unsigned short int
(rather than int).
hh As for h, but the next pointer is a pointer to a signed char or unsigned
char.
The C library in eCos implements as follow:
again:
c = *fmt++
switch (c) {
...
case 'h':
flags |= SHORT;
goto again;
...
}
it results that it treat "hh" as "h".
When we try to did something like this:
unsigned char c;
sscanf(str, "%hhx", &c);
a segmentfault was generated.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2015-12-04 1:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 1:41 bugzilla-daemon [this message]
2015-12-04 1:44 ` [Bug 1002110] " bugzilla-daemon
2015-12-08 20:44 ` bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2015-12-04 1:41 [Bug 1002110] 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-1002110-777@http.bugs.ecos.sourceware.org/ \
--to=bugzilla-daemon@ecoscentric.com \
--cc=unassigned@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).