Article ID: 259726
Article Last Modified on 8/7/2007
APPLIES TO
- Microsoft Visual C++ 6.0 Enterprise Edition
- Microsoft Visual C++ 6.0 Professional Edition
- Microsoft Visual C++ 6.0 Standard Edition
- The Integrated Debugger
This article was previously published under Q259726
SYMPTOMS
When you debug your code locally, you may encounter invisible breakpoints in the Visual C++ Debugger when you single step or step over certain assembly instructions.
On a Microsoft Windows 2000-based computer, remote debugging may stop responding (hang).
CAUSE
This occurs because of a bug in the debugger.
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected in the latest service pack for Visual Studio 6.0.
For additional information about Visual Studio service packs, click the following article numbers to view the articles in the Microsoft Knowledge Base:
194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why
194295 HOWTO: Tell That a Visual Studio Service Pack Is Installed
To download the latest Visual Studio service pack, visit the following Microsoft Web site:
MORE INFORMATION
The behavior described in the "Symptoms" section can appear in the following assembly instructions.
When stepping into:
INSB,INSW,OUTSB,OUTSW,PUSHFD,POPFD,CLI,STI,IRET.
-or-
When stepping over:
INSB,INSW,OUTSB,OUTSW,MOVSB,MOVSW,CMPSB,CMPSW,STOSB,STOSW,LODSB,LODSW,SCASB ,SCASW.
Additional query words: sp4
Keywords: kbbug kbdebug kbfix kbide kbvs600sp4fix kbvs600sp5fix KB259726
