Debugging Timer Functions Requires Hard-Mode Debugging

 Last reviewed: July 22, 1997
Article ID: Q131897
1.00 1.50 1.51 1.52 WINDOWS kbtool kbtshoot

The information in this article applies to:

  • The integrated debugger included with: Microsoft Visual C++ for Windows, versions 1.0, 1.5, 1.51, 1.52

SUMMARY

When setting a breakpoint in a Windows timer function (TimerProc), you might receive this error message: 

   Cannot process breakpoint while debugger already stopped
To resolve this, you need to place the debugger into hard mode. On the Options menu, click Debug, and then choose Hard as the debugging mode.

MORE INFORMATION

By placing the debugger into hard mode, you ensure that the application cannot start or switch to any other applications. This makes the application "task exclusive," and all keyboard and mouse messages are sent only to the debugger and its target application.

There are times when the debugger may destabilize Windows by interacting with it. This can happen when the debugger stops while the system is in a critical (non-interruptable) processing stage (stopping at a breakpoint, stepping through code, encountering an exception, and so on). This can occur while debugging things like menu events, system modal windows, or intertask messages.

Hard-mode debugging is especially useful when debugging time-critical events such as timer events and intertask DDE transactions.

NOTE: Hard-mode debugging is not available when you are using the 16-bit debugging environment under Windows NT.

Additional reference words: kbinf 1.00 1.50
KBCategory: kbtool kbtshoot
KBSubcategory: WBDebug
Keywords : kb16bitonly

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: July 22, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.