Tracing into a Macro When Debugging Assembly Programs

Last reviewed: January 6, 1995
Article ID: Q67440

The information in this article applies to:

Microsoft Macro Assembler for MS-DOS and OS/2, versions 5.1, 6.0, 6.0a, and 6.0b

When you use a macro in an assembly-language routine and you are debugging, you cannot trace into the macro definition as you can with a procedure. The debugger simply executes the macro call (steps over it) as if it were a single instruction.

This behavior is by design. There is no symbolic information generated to allow the debugger to step into the macro. If you are using CodeView, you can switch to assembler mode (not source mode) and single step through the code. However, if you are using Microsoft Quick Assembler, you will have to expand the macro before assembly if you want to step through the code.

Note: There is a CodeView update for Quick Assembler version 2.51 owners. Call Microsoft Sales and Service at (800) 426-9400 for more information.

Additional reference words: 5.10 6.00 6.00a 6.00b
KBCategory: kbtool
KBSubCategory: MLIss

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.

Last reviewed: January 6, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.