fclose requires as its argument a FILE pointer obtained either by fopen, one of the standard streams stdin, stdout, or stderr, or in some other implementation-defined way. A null pointer is not one of these, so the behavior is undefined, just like fclose((FILE *)0xdeadbeef) would be. NULL is not special in C; aside from the … Read more
Why is it I get segmentation faults instead? The segmentation fault, what you’re seeing, is a side-effect of the stack overflow. The reason is stack overflow, the result is segmentation fault. From the wikipedia article for “stack overflow” (emphasis mine) …. When a program attempts to use more space than is available on the call … Read more
Weird Native Crash – pid: 0, tid: 0 signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
env SEGFAULT_SIGNALS=”abrt segv” LD_PRELOAD=/lib/libSegFault.so someapp Note that the actual path to the preload library may differ. On my machine, I’d use env SEGFAULT_SIGNALS=”abrt segv” LD_PRELOAD=/lib/x86_64-linux-gnu/libSegFault.so some-64bit-app or env SEGFAULT_SIGNALS=”abrt segv” LD_PRELOAD=/lib/i386-linux-gnu/libSegFault.so some-32bit-app depending whether the application I was running was compiled 64-bit or 32-bit. (You can use file to check.) The source tells us there … Read more
There’s no way to say from just that code. Most likely, you are passing in a pointer that points to invalid memory, non-modifiable memory or some other kind of memory that just can’t be processed the way you process it here. How do you call your function? Added: You are passing in a pointer to … Read more
The word main is a legal name for any variable. The typical use case is to provide a function of the name main to a compiler, which compiles it to an object file, which in turn is linked to with crt0.o that provides initialization for run-time (stack allocation etc.) and jumps to the label main. … Read more
You can use command thread apply all bt or thread apply all bt full to get backtraces of all threads. Might be useful. By the way if you get rid of you handler will your OS create a core file?
What you are doing is undefined behavior. The compiler is allowed to assume that you will never use more than sizeof int64_t for the variable member int64_t c. So if you try to write more than sizeof int64_t(aka sizeof c) on c, you will have an out-of-bounds problem in your code. This is the case … Read more
You need a page with write execute permissions. See mmap(2) and mprotect(2) if you are under unix. You shouldn’t do it using malloc. Also, read what the others said, you can only run raw machine code using your loader. If you try to run an ELF header it will probably segfault all the same. Regarding … Read more