BUG: Remote Windows 95 Machine Crashes on Stop Debugging

 Last reviewed: May 21, 1997
Article ID: Q167358
The information in this article applies to:
  • The integrated debugger included with: - Microsoft Visual C++, 32-bit Editions, version 5.0

SYMPTOMS

If the remote machine is a Windows 95 machine and Stop Debugging is selected inside the InitInstance member function of a default Appwizard generated application, Developer Studio hangs on the local machine. If you kill Developer Studio from Task Manager, the remote Windows 95 machine crashes and must be restarted.

RESOLUTION

Using single stepping (F10 or F11) or Debug Go (F5), return from the InitInstance function so that the main window of the application is visible. Now you can safely select Stop Debugging.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

The behavior is seen if the remote computer is a Windows 95 machine. The local computer could be a Windows NT or a Windows 95 computer.

Steps to Reproduce Behavior

  1. Create a default Appwizard generated MFC application and build it as Debug build.

  2. Set the local computer and remote computer for remote debugging.

  3. Set a break point at the following line in the application's InitInstance function: 

          pMainFrame->ShowWindow(m_nCmdShow);

  4. Start debugging by selecting Build|Start Debug|Go, or hitting the F5 key. The debugger will stop at the above line of code.

  5. Hit F10 (Step Over) or F11 key (Step Into) to go to next line of code. You will see an outline of the application window on the remote computer.

  6. Select Stop Debugging. A Debug Assertion in the remote computer (you may Abort or Retry) occurs, and Developer Studio hangs on the local computer.

  7. Kill Developer Studio from Task Manager to crash the remote computer.

Keywords : kbtool vcbuglist500 VWBIss WBDebug kbbuglist
Version : 5.0
Platform : NT WINDOWS
Issue type : kbbug

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