Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m writing error handling code for a server on FreeBSD. For extremely serious errors I want to avoid data corruption by immediately terminating. That’s easy, exit(3). Before I exit, I output my relevant variables that led me there. However, ideally, this termination would be accompanied by a .core so that I could fully investigate what got me to this catastrophic (and likely hard to reproduce) state.
How can I force this to happen?
kill -QUIT process_idwill cause a core dump from a running process (assuming that resource limits allow it).Or see
man 3 abortfor causing a program to dump itself.Added: From an interactive shell, a running program can be made to abort with the quit key, usually Ctrl+\, which sends a SIGQUIT just as the more common Ctrl+C sends a SIGINT. This is identical to the
kill -QUIT…it’s just easier to type if you are on the controlling terminal. Seeman 1 sttyif your default quit key is different.