Details
-
Task
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
Description
MariaDB uses the lowest possible details level for the MiniDumpWriteDump call here (server/mysys/stacktrace.c):
/* Create minidump */
|
if(MiniDumpWriteDump(GetCurrentProcess(), GetCurrentProcessId(),
|
hFile, MiniDumpNormal, &info, 0, 0))
|
{
|
my_safe_printf_stderr("Minidump written to %s\n",
|
_fullpath(path, dump_fname, sizeof(path)) ?
|
path : dump_fname);
|
}
|
According to https://msdn.microsoft.com/en-us/library/windows/desktop/ms680519(v=vs.85).aspx
"MiniDumpNormal
Include just the information necessary to capture stack traces for all existing threads in a process."
While this produces the smallest possible minidumps that are still useful for getting backtraces and values for some of local variables, it would be great to include everything but InnoDB buffer pool and query cache.
Also, adding PID of the process to the file name in addition to the executable name would be useful as an option, otherwise minidumps created with --core-file option overwrite each other.
See https://bugs.mysql.com/bug.php?id=72284 for more details.