PRB: Debugging an Application Driven by MS-TEST

 Last reviewed: November 2, 1995
Article ID: Q100957
The information in this article applies to:
  • Microsoft Win32 Software Development Kit (SDK), versions 3.1, 3.5, 3.51, and 4.0

SYMPTOMS

When an application driven by MS-TEST is being debugged by WinDbg or NTSD (for example, after an exception has occurred), both the application and the debugger hang.

CAUSE

The debugger is hooked and ends up hanging.

RESOLUTION

It is not possible to use NTSD or WinDbg to debug an application that is driven by MS-TEST. Use Dr. Watson (drwtsn32) instead. Note that you must turn off Visual Notification.

Additional reference words: 3.10 3.50 4.00 95
KBCategory: kbtool kbprb
KBSubcategory: TlsWindbg

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: November 2, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.