Full Question:
In most case, it should come from incorrect use of memory. If the codes is never changed while using debugger, time of random numbers are problematic. For example, for index of array, it might be using time, or perhaps random numbers. Or it does nasty things with memory. So 'out of bounds of array' might be shown.
Other possible answers can exist. For example,
There might be multiple recursions in the code which are causing a stack overflow, cause "Out Of Memory".
A probable cause would be an uninitialized pointer/variable being used. Or it is possible that pointer variables have wrong value.
You are given a the source to a application which is crashing when run. After running it 10 times in a debugger, you find it never crashes in the same place. The application is single threaded, and uses only the C standard library. What programming errors could be causing this crash? How would you test each one?
In most case, it should come from incorrect use of memory. If the codes is never changed while using debugger, time of random numbers are problematic. For example, for index of array, it might be using time, or perhaps random numbers. Or it does nasty things with memory. So 'out of bounds of array' might be shown.
Other possible answers can exist. For example,
There might be multiple recursions in the code which are causing a stack overflow, cause "Out Of Memory".
A probable cause would be an uninitialized pointer/variable being used. Or it is possible that pointer variables have wrong value.
You are given a the source to a application which is crashing when run.