[MDEV-15659] Consider using better options for MiniDumpWriteDump Created: 2018-03-25 Updated: 2018-03-25 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Platform Windows |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Valerii Kravchuk | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | upstream | ||
| Description |
|
MariaDB uses the lowest possible details level for the MiniDumpWriteDump call here (server/mysys/stacktrace.c):
According to https://msdn.microsoft.com/en-us/library/windows/desktop/ms680519(v=vs.85).aspx "MiniDumpNormal 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. |