I would like to force a core dump at a specific location in my C++ application.
I know I can do it by doing something like:
int * crash = NULL;
*cras
Invoke
abort();
Related, sometimes you'd like a back trace without an actual core dump, and allow the program to continue running: check out glibc backtrace() and backtrace_symbols() functions: http://www.gnu.org/s/libc/manual/html_node/Backtraces.html
Sometimes it may be appropriate to do something like this:
int st = 0;
pid_t p = fork();
if (!p) {
signal(SIGABRT, SIG_DFL);
abort(); // having the coredump of the exact copy of the calling thread
} else {
waitpid(p, &st, 0); // rip the zombie
}
// here the original process continues to live
One problem with this simple approach is that only one thread will be coredumped.
A few years ago, Google released the coredumper library.
Overview
The coredumper library can be compiled into applications to create core dumps of the running program -- without terminating. It supports both single- and multi-threaded core dumps, even if the kernel does not natively support multi-threaded core files.
Coredumper is distributed under the terms of the BSD License.
Example
This is by no means a complete example; it simply gives you a feel for what the coredumper API looks like.
#include <google/coredumper.h> ... WriteCoreDump('core.myprogram'); /* Keep going, we generated a core file, * but we didn't crash. */
It's not what you were asking for, but maybe it's even better :)
#include <assert.h>
.
.
.
assert(!"this should not happen");
#include <stdlib.h> // C
//#include <cstdlib> // C++
void core_dump(void)
{
abort();
}
Another way of generating a core dump:
$ bash
$ kill -s SIGSEGV $$
Just create a new instance of the bash and kill it with specified signal. The $$
is the PID of
the shell. Otherwise you are killing your current bash and will be logged out, terminal closed or disconnected.
$ bash
$ kill -s SIGABRT $$
$ bash
$ kill -s SIGFPE $$