You can get this error when the compiler gets too confused about what’s going on in your code. I noticed you have a number of what appear to be functions nested within functions. You might try commenting out some of that at a time to see if the error goes away. That way you can … Read more
GCC can’t do that but GDB (a debugger) sure can. Compile you program using the -g switch, like this: gcc program.c -g Then use gdb: $ gdb ./a.out (gdb) run <segfault happens here> (gdb) backtrace <offending code is shown here> Here is a nice tutorial to get you started with GDB. Where the segfault occurs … Read more
First, get your tombstone stack trace, it will be printed every time your app crashes. Something like this: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Build fingerprint: ‘XXXXXXXXX’ pid: 1658, tid: 13086 >>> system_server <<< signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 64696f7e r0 00000000 … Read more
See the C FAQ, Question 1.32 Q: What is the difference between these initializations? char a[] = “string literal”; char *p = “string literal”; My program crashes if I try to assign a new value to p[i]. A: A string literal (the formal term for a double-quoted string in C source) can be used in … Read more
Bus errors are rare nowadays on x86 and occur when your processor cannot even attempt the memory access requested, typically: using a processor instruction with an address that does not satisfy its alignment requirements. Segmentation faults occur when accessing memory which does not belong to your process. They are very common and are typically the … Read more
Segmentation fault is a specific kind of error caused by accessing memory that “does not belong to you.” It’s a helper mechanism that keeps you from corrupting the memory and introducing hard-to-debug memory bugs. Whenever you get a segfault you know you are doing something wrong with memory – accessing a variable that has already … Read more