Program Database (PDB) files (with file name extension
pdb) are included in ZIP Archive
distributions (but not MSI distributions) of MySQL. These
files provide information for debugging your MySQL
installation in the event of a problem.
As of MySQL 5.7.6, the PDB files are available in a separate file labeled "ZIP Archive Debug Binaries & Test Suite".
The PDB file contains more detailed information about
mysqld and other tools that enables more
detailed trace and dump files to be created. You can use these
with WinDbg or Visual Studio to debug
The older Dr. Watson debugging tool was removed in Microsoft Vista, with WinDbg being a common alternative. Both methods are documented here.
To use WinDbg, either install the full Windows Driver Kit (WDK) or install the standalone version.
.pbd files must be an exact match
(both version number and MySQL server edition) or WinDBG
will complain while attempting to load the symbols.
To generate a minidump
mysqld.dmp, enable the
core-fileoption under the [mysqld] section in
my.ini. Restart the MySQL server after making these changes.
Create a directory to store the generated files, such as
Determine the path to your windbg.exe executable using the Find GUI or from the command line, for example:
dir /s /b windbg.exe-- a common default is C:\Program Files\Debugging Tools for Windows (x64)\windbg.exe
windbg.exegiving it the paths to
mysqld.dmp, and the source code. Alternatively, pass in each path from the WinDbg GUI. For example:
windbg.exe -i "C:\mysql-5.5.49-winx64\bin\"^ -z "C:\mysql-5.5.49-winx64\data\mysqld.dmp"^ -srcpath "E:\ade\mysql_archives\5.5\5.5.49\mysql-5.5.49"^ -y "C:\mysql-5.5.49-winx64\bin;SRV*c:\symbols*http://msdl.microsoft.com/download/symbols"^ -v -n -c "!analyze -vvvvv"Note
^character and newline are removed by the Windows command line processor, so be sure the spaces remain intact.
To generate a crash file using Dr Watson (for Microsoft Vista and below), follow these steps:
Start Dr Watson by running drwtsn32.exe interactively using the
Set the Log File Path to the directory where you want to store trace files.
Make sure Dump All Thread Contexts and Append To Existing Log File.
Uncheck Dump Symbol Table, Visual Notification, Sound Notification and Create Crash Dump File.
Set the Number of Instructions to a suitable value to capture enough calls in the stacktrace. A value of at 25 should be enough.
Note that the file generated can become very large.