C：malloc似乎分配更多然后我请求（数组）

Question

Hi I have this question: Why when I'm allocating memory with malloc for a float array, it allocate more space that i'm requesting? For example in this code i'm trying to allocate a ten "cells" float array, but if I try to access to other cells it returns me no segfault error:

#include <stdio.h>
#include <stdlib.h>
#include <string.h>

float *fk_array;

int main(int argc, char** argv){


    fk_array = (float *) malloc(10 * sizeof(float));
    int i;
    fk_array[9] = 2.23;
    fk_array[15] = 0.3;
    for(i = 0; i<20 ; i++)
        printf("%f\n",fk_array[i]);
    free(fk_array);

    return 1;
}

It returns me :

0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
0.000000
2.230000
0.000000
0.000000
0.000000
0.000000
0.000000
0.300000
0.000000
0.000000
0.000000
0.000000

Where I'm in wrong??

Answer 1

It's not unlikely that, depending on allocation algorithm, that more is allocated than you request. However, accessing that memory is undefined behavior .

Answer 2

When calling malloc , additional space may used to store metadata about the allocated block, such as its size and information about other allocated blocks. Sometimes the implementation prefers allocated blocks to be at specific intervals (eg, multiples of 4 or 8 bytes). However, you shouldn't depend on the amount of space being consistent each time you call malloc ; use only what you have specifically requested or you may be overwriting other important information.

See the answers to the following questions for more information:

• How do free and malloc work in C?
• Why does malloc allocate a different number of bytes than requested?

Answer 3

I would not be surprised if allocating heap memory does not fall into specific processor rules that addresses must be aligned on a long, quad, or other boundary.

So, if you requested 100 bytes of heap space, the OS may return more than you requested to satisfy alignment requirements of the processor. However, accessing more than the 100 bytes is considered undefined and can and probably will result in a lot of strange behavior you do not want.

Answer 4

You can only get a segmentation fault if a read or write falls in the wrong page . A page is typically 4KiB.

The malloc() system call may reserve a bit more space than requested, and it reserves a few words of memory before the block for book-keeping, but that your program does not get killed when accessing fk_array[15] does not mean that it did not access outside the block reserved for it. It probably did, the OS just didn't notice it. If you had allocated another array after allocating fk_array , you would have had a chance to notice that it was changing.