Why do loop it for 44 times I don’t get it. But when I changed 44 to 3 in the loop it works.
for (i = 0; i < 3; i++)
Depends on your compiler though but in case of 44 iteration windows gives me message application not responding.
More Related Contents:
- C/SDL – Segmentation fault when program run multiple times in succession [closed]
- Why is this segfaulting? Can someone explain the valgrind error?
- Segmentation fault, I don’t know why
- Making an array using pointers in c
- my code does not work and I don’t know why ;-;
- Why do I get a segmentation fault when writing to a “char *s” initialized with a string literal, but not “char s[]”?
- How do I properly compare strings in C?
- Crash or “segmentation fault” when data is copied/scanned/read to an uninitialized pointer
- Why is this string reversal C code causing a segmentation fault? [duplicate]
- What is a bus error? Is it different from a segmentation fault?
- String literals: pointer vs. char array
- Segmentation Fault, large arrays
- Why does this code segfault on 64-bit architecture but work fine on 32-bit?
- segmentation fault using scanf [duplicate]
- Why does strcmp() return 0 when its inputs are equal?
- Execution of printf() and Segmentation Fault
- What does strcmp() exactly return in C?
- C – Segmentation Fault with strcmp?
- Returning pointer from a function
- strcmp() return values in C [duplicate]
- casting char[][] to char** causes segfault?
- strtok segmentation fault
- SegFault after scanf?
- What is the simplest standard conform way to produce a Segfault in C?
- Pointer initialisation gives segmentation fault
- Segmentation fault in btree implementation
- strlen not checking for NULL
- Segmentation fault when allocating large arrays on the stack
- Implementation of strcmp
- strncpy leading to segmentation fault