How does this work

Question

I was looking at the lessons for C and was playing around with the code and tried this:

#include <stdio.h>

int main() {
int x[] = {20, 45, 16, 18, 22};
x[1] = 260;
x[7] = 370;
printf("The second element is %d\n", x[1]); /* 260 */
printf("The 8th element is %d\n", x[7]);
printf("The 7th element is %d\n", x[6]);
return 0;
}

Why does it say that the last output's value is 8?
https://code.sololearn.com/cw5k953k8s94/?ref=app

Answer 1

Modifying elements beyond the array bounds introduces bugs into the program. Note how I modified b[3] and the value of a changed. This is the worst type of bug to track down.
https://code.sololearn.com/cqImm6YcHWd4

Answer 2

It's some Garbage value... Paul had written a code about it too in C++... (sorry to bother you bro)

https://code.sololearn.com/c6AUk70emKRg/?ref=app

Answer 3

@Saad OK thanks

Answer 4

Its a dummy value. It is auto assigned. There will be something in x[5] and x[8] too..
It is to prevent memory leak. That’s why it is recommended to assign every value or use arrays in sequence

Answer 5

Yes, you failed to assign a value.
But the reason you get that value is that an array (or variable) that's not initialised will _contain whatever values were left in memory_ prior to declaration. Values are the same on SL because the playground is probably emulated. On a PC these values _may change_ after running another program or rebooting.

Note: you shouldn't be accessing that area of memory at all since x was declared as having 5 elements.

Answer 6

True! Asterisk

Answer 7

When did you assign any value to x[6]?

Answer 8

I didnt

Answer 9

yeh its garbage value $hardul Birje but it seem that of sololearn is given an integer as it garbage value that why it seem confusing, while that of a computer will be given hexadecimal value as it garbage value