| Bug #21696 | Add information about Program Database Files (pdb) | ||
|---|---|---|---|
| Submitted: | 17 Aug 2006 13:11 | Modified: | 14 Sep 2007 9:05 |
| Reporter: | Miguel Solorzano | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
| Version: | 5.0 (all ?) | OS: | Windows (Windows) |
| Assigned to: | MC Brown | CPU Architecture: | Any |
[14 Sep 2007 9:05]
MC Brown
A new section has been added to detail how to use PDB files and enable traces within Windows to the 5.1, 5.2 and 5.0 reference manuals.
Description: From version 5.0.24 the Windows server binaries were compiled with debugging symbols and generated/packed their pdb files: C:\mysql\bin>dir *.pdb Volume in drive C has no label. Volume Serial Number is C0FB-E588 Directory of C:\mysql\bin 28/07/2006 13:05 12.086.272 mysqld-debug.pdb 28/07/2006 13:05 4.230.144 mysqld-max-nt.pdb 28/07/2006 13:05 4.221.952 mysqld-max.pdb 28/07/2006 13:05 3.787.776 mysqld-nt.pdb 28/07/2006 13:05 3.787.776 mysqld.pdb 28/07/2006 13:05 1.321.984 mysqlmanager.pdb 6 File(s) 29.435.904 bytes 0 Dir(s) 7.724.367.872 bytes free Then would be nice to have instructions why these files were added in the release package, how to setup/use a JIT debugger Windows (Dr. Watson/WinDBG) for to generate a dump/log files and so on. How to repeat: See description. Suggested fix: -