CareerCup

@Barney, @luv, I want to share some of my concepts.
I request you to get your basic concepts clear & brushed up.
When you are calling f(), then memory is being allocated for array a[] on the stack, where you are initializing its sots with 1. Now, since this array has been allocated on the stack, the scope is local. When you return from the function, the memory gets freed up. However memory doesn't go anywhere. The OS maintains a free list of all the memory which has been freed & so, can be used by any other process. By garbage value, the process means that it is expecting any unusual value[it may mean 1 or value with figure like 84638290(Both are considered as garbage for that process)].
Now, coming to the point, When you call function g(), memory is being allocated for array b[], However, its just an accident that the same memory gets allocated that was being allocated to a[] & so, it contains all 1.
However, its never safe to rely upon such type of allocation[as its just an accident].
A different compiler, a different optimization settings would trap you.

Hope everything is clear.

It prints garbage value .... not a 12 times 1...

1073836921
0
-1078604124
1074324994
1075105060
1075105048
-1078604284
1073841448
1073841184
1073831176
1073829312
1073844912

Garbage value.

Garbage values will be printed.

garbage value.....because array allocated memory on stack(ie at compile time) and stack memory contain same garbage value that y it print garbage.

garbage value will be printed

Output will be...

1
1
1
1
1
1
1
1
1
1
1
1

12 times 1....

for array greater than 12 it will print some of a and some of garbage value