For each custom kernel configuration directory

Question

Is there a way to configure the directory where the core dump files are stored for a specific process?

I have a daemon process written in C ++ for which I would like to configure a kernel dump directory. If desired, the file template should also be customized.

I know about /proc/sys/kernel/core_pattern , however this would change the structure of templates and directories all over the world.

Apache has a CoreDumpDirectory directive - so it's possible.

Answer 1

No, you cannot install it for each process. The main file is dumped either to the current working directory of the process, or to the directory installed in / proc / sys / kernel / core _pattern if the template contains a directory.

CoreDumpDirectory in apache is a hack, apache registers signal handlers for all signals that cause a core dump, and changes the current directory in its signal handler.

 /* handle all varieties of core dumping signals */ static void sig_coredump(int sig) { apr_filepath_set(ap_coredump_dir, pconf); apr_signal(sig, SIG_DFL); #if AP_ENABLE_EXCEPTION_HOOK run_fatal_exception_hook(sig); #endif /* linuxthreads issue calling getpid() here: * This comparison won't match if the crashing thread is * some module thread that runs in the parent process. * The fallout, which is limited to linuxthreads: * The special log message won't be written when such a * thread in the parent causes the parent to crash. */ if (getpid() == parent_pid) { ap_log_error(APLOG_MARK, APLOG_NOTICE, 0, ap_server_conf, "seg fault or similar nasty error detected " "in the parent process"); /* XXX we can probably add some rudimentary cleanup code here, * like getting rid of the pid file. If any additional bad stuff * happens, we are protected from recursive errors taking down the * system since this function is no longer the signal handler GLA */ } kill(getpid(), sig); /* At this point we've got sig blocked, because we're still inside * the signal handler. When we leave the signal handler it will * be unblocked, and we'll take the signal... and coredump or whatever * is appropriate for this particular Unix. In addition the parent * will see the real signal we received -- whereas if we called * abort() here, the parent would only see SIGABRT. */ }