Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    a segfault should produce a core dump if the ulimit allows it. Inspect the core dump with gdb. Commented Apr 4, 2013 at 21:48
  • 1
    The kernel logs when a processes is killed by oom-killer. Even if you can't inspect /var/log, you should be able to access the kernel log buffer with the dmesg command so you can rule this possibility out. Commented Apr 5, 2013 at 16:47
  • Getting a core dump allowed me to figure out the underlying problem: a data race condition, where a file could get created and then noticed by my program. The file could get deleted before my program tried to open it. I didn't handle ENOENT correctly, causing problems up the call stack. Commented Apr 17, 2013 at 17:52