Q49067: QuickC and QuickAssembler Cannot Debug Code in Include Files

Article: Q49067
Product(s): See article
Version(s): 2.01
Operating System(s): MS-DOS
Keyword(s): ENDUSER | docerr S_QuickC S_CodeView | mspl13_masm
Last Modified: 10-OCT-1989

The QuickC and QuickAssembler environment debuggers do not allow the
debugging of executable code in include files. The problem occurs when
stepping through the program using the F8 key. When the debugger
encounters the line containing the include statement, the debugger
attempts to execute the code that is outside of the main module, with
unpredictable results.

The explanation of the include directive for assembly programs on Page
240 of the Microsoft "QuickAssembler Programmer's Guide" is unclear.
This explanation notes that "any standard code can be placed in an
include file." However, it is not mentioned in this explanation that
subsequent problems will arise when attempting to debug these
routines.

This problem is related to the way in which symbolic information is
coded and is a known limitation of the QuickAssembler and QuickC
debuggers, as well as the CodeView debugger.

The solution to this problem is to include only macros, equates, and
standard segment definitions in the include files when 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.

Copyright Microsoft Corporation 1986-2002.