Microsoft KB Archive/140444

= FIX: UNC File Names Cause Remote Debugging to Fail =

Article ID: 140444

Article Last Modified on 12/9/2003

-

APPLIES TO

 The Integrated Debugger, when used with:  Microsoft Visual C++ 4.0 Standard Edition

 Microsoft Visual C++ 4.1 Subscription

 Microsoft Visual C++ 4.2 Enterprise Edition

 Microsoft Visual C++ 4.2 Professional Edition</li></ul> </li></ul>

-

<div class="notice_section">

This article was previously published under Q140444

<div class="symptoms_section">

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.

<div class="cause_section">

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: <pre class="fixed_text">  \\server\share\myproj\myprog.exe

<div class="resolution_section">

RESOLUTION
To work around this problem, map a drive to the share and use the mapped file name. For example, from the host computer: <pre class="fixed_text">  p: = \\server\share

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

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

<div class="status_section">

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.

Additional query words: kbVC400bug

Keywords: kbbug kbfix kbide kbvc500fix kbdebug KB140444

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.