Heap Damage in C

Question

int main ()
{
    int * b;
    b = (int*) malloc (1);
    *b=110000;
    free (b);
    return 0;
}

Why does a bunch happen when free (b);?

IMO, heap damage already occurs at *b=110000;.

Answer 1

malloc()An argument is the number of bytes to place. You need to use:

b = (int*) malloc(sizeof(int));

You allocated a block too small, and then wrote more bytes than you allocated, which overwrites the accounting information next to the block, corrupting the heap.

Answer 2

* b = 110000; , int , . b = (int *) malloc (sizeof (int)), int * b char * b, malloced char *. , , 128 (- char) * b.

EDIT: - , - . .

Answer 3

*b=11000, free(b), , .

( ) , . , malloc free ( ).

Answer 4

, , , .

char *, int *, -128 127 * b .