KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q47029: .DBG File Needed to Debug .COM File

Article: Q47029
Product(s): See article
Version(s): 2.01
Operating System(s): MS-DOS
Keyword(s): ENDUSER | | mspl13_masm
Last Modified: 26-JUL-1989

To debug a .COM file produced with the QuickAssembler, the linker
places necessary symbolic information in a file with the extension
.DBG. If this file is deleted, no error message is issued, but the
QuickAssembler will report that the program does not contain debug
information. At this point, it asks if you would like to rebuild with
the debug information. In general, you should do this rebuild so that
you can use the full power of the QuickAssembler debugger.

If you choose not to rebuild by selecting "No", then any debugging
command that requires debugging information, including breakpoints and
displays of variables by name, will be unavailable. Because of this,
Microsoft recommends rebuilding to include debugging information
before debugging.

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.