99.9% likely that you have corrupted memory (over- or under-flowed a buffer, wrote to a pointer after it was freed, called free twice on the same pointer, etc.)
Run your code under Valgrind to see where your program did something incorrect.
More Related Contents:
- Why does malloc initialize the values to 0 in gcc?
- aligned malloc() in GCC?
- Why do I get different results when I dereference a pointer after freeing it?
- difference between and
- Why do I get a warning every time I use malloc?
- An alternative for the deprecated __malloc_hook functionality of glibc
- Why does malloc allocate a different number of bytes than requested?
- Why is scanf() causing infinite loop in this code?
- What REALLY happens when you don’t free after malloc before program termination?
- Is gcc’s __attribute__((packed)) / #pragma pack unsafe?
- Is bool a native C type?
- Where is the header file on Linux? Why can’t I find ? [duplicate]
- Setting variable to NULL after free
- Is there a way to use gcc to convert C to MIPS?
- typedef fixed length array
- What is the use of _start() in C?
- C: for loop int initial declaration
- Why does passing char** as const char** generate a warning?
- What is the advantage of GCC’s __builtin_expect in if else statements?
- C Failing to compile: Can’t find math.h functions [duplicate]
- Why do we cast return value of malloc? [duplicate]
- Disable warning: the `gets’ function is dangerous in GCC through header files?
- Find malloc() array length in C? [duplicate]
- Why can’t the size of a static array be made variable?
- x86_64 : is stack frame pointer almost useless?
- calling assembly function from c
- How do I link object files in C? Fails with “Undefined symbols for architecture x86_64”
- Array of size 0 at the end of struct [duplicate]
- Returning struct containing array
- & operator optional in function pointer assignment