FIX: UNC File Names Cause Remote Debugging to Fail

 Last reviewed: September 19, 1997
Article ID: Q140444
The information in this article applies to:
  • The integrated debugger included with: - Microsoft Visual C++, 32-bit Edition, versions 4.0, 4.1, 4.2

SYMPTOMS

A remote debugging session hosted on Windows NT with the target located on a computer running Windows 95 using TCP/IP may fail to acknowledge breakpoints. In addition, pressing CTRL+BREAK interrupts the debugging session leaving you with assembler code rather than source code in the source window.

CAUSE

On the host computer, the Debug tab in the Project Settings dialog box has two executable location fields:

  • Executable for debug session {full executable name as it appears to the host PC}.
  • Remote executable path and file name {full executable name as it appears to the remote PC}.

Using a UNC file specification for these fields results in the same entry in both fields. For example: 

   \\server\share\myproj\myprog.exe

RESOLUTION

To work around this problem, map a drive to the share and use the mapped file name. For example, from the host computer: 

   p: = \\server\share

   Executable for debug session: p:\myproj\myprog.exe

   Remote executable path and file name: c:\myproj\myprog.exe

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug was corrected in Visual C++ version 5.0. 

Keywords          : vcbuglist400 vcfixlist500 WBDebug kbtool
Version           : 4.0 4.1 4.2
Platform          : NT WINDOWS
Issue type        : kbbug
Solution Type     : kbfix

================================================================================

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