PRB: Debuggers Cannot Reliably Use Debug Register Breakpoints

Article translations Article translations
Article ID: 137199 - View products that this article applies to.
This article was previously published under Q137199
Expand all | Collapse all

SYMPTOMS

Debug register breakpoints are breakpoints that trigger on write or read of a specific memory location. If you use debug register breakpoints in application debuggers such as CodeView, Visual C++, or Windbg, other applications in the system could fault.

CAUSE

Debug registers are not saved and restored on a per application basis in Windows 95; they are global to the system.

A debug register running at the same address (but in another memory context) could trigger that debug breakpoint. Because there may not be a debugger registered to handle the breakpoint in the second application, Windows 95 interprets this as an unhandled exception. In most cases, this causes Windows 95 to terminate the second application, even though it had nothing to do with the problem.

RESOLUTION

To work around this problem, use a system level debugger such as Soft-ICE or WDEB386, or avoid using debug register breakpoints.

STATUS

This behavior is by design.

Properties

Article ID: 137199 - Last Review: February 22, 2007 - Revision: 2.1
APPLIES TO
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Win32 Software Development Kit (SDK) 4.0
Keywords: 
KB137199

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com