@thomasorus I'd recommend you run that in a debugger. My preference is either for nemiver or better yet, the eclipse c standalone debugger. I'd help you more, but I'd need to be at a computer and Not on a phone.
Anyhow if you rerun your code within a debugger it will at least (probably) pinpoint the line which triggered the segfault.
@thomasorus Excellent, and don't forget to make sure you recompile your code with debugging symbols on (i.e., include the `-ggdb` flag when compiling) before trying to debug it. Otherwise the debuggers will show you disassembly instead, which isn't so helpful.
@leimon @thomasorus address sanitizer should help too.
@leimon Thanks I’ll try it tomorrow evening!