Potential problem with C standard malloc'ing chars.
Posted
by paxdiablo
on Stack Overflow
See other posts from Stack Overflow
or by paxdiablo
Published on 2009-10-08T01:25:01Z
Indexed on
2010/05/19
1:40 UTC
Read the original article
Hit count: 251
When answering a comment to another answer of mine here, I found what I think may be a hole in the C standard (c1x, I haven't checked the earlier ones and yes, I know it's incredibly unlikely that I alone among all the planet's inhabitants have found a bug in the standard). Information follows:
- Section 6.5.3.4 ("The sizeof operator") para 2 states
"The sizeof operator yields the size (in bytes) of its operand"
. - Para 3 of that section states:
"When applied to an operand that has type char, unsigned char, or signed char, (or a qualified version thereof) the result is 1"
. - Section 7.20.3.3 describes
void *malloc(size_t sz)
but all it says is"The malloc function allocates space for an object whose size is specified by size and whose value is indeterminate"
. It makes no mention at all what units are used for the argument. - Annex E startes the 8 is the minimum value for
CHAR_BIT
so chars can be more than one byte in length.
My question is simply this:
In an environment where a char is 16 bits wide, will malloc(10 * sizeof(char))
allocate 10 chars (20 bytes) or 10 bytes? Point 1 above seems to indicate the former, point 2 indicates the latter.
Anyone with more C-standard-fu than me have an answer for this?
© Stack Overflow or respective owner