BUG: You may receive an error message when you try to save a dump file during a remote debugging session in the Visual Studio .NET IDE (814794)



The information in this article applies to:

  • Microsoft Visual Studio .NET (2002), Professional Edition
  • Microsoft Visual Studio .NET (2002), Enterprise Architect Edition
  • Microsoft Visual Studio .NET (2002), Enterprise Developer Edition
  • Microsoft Visual Studio .NET (2002), Academic Edition

SYMPTOMS

When you try to save a dump file of the remote debugging session from the Visual Studio .NET IDE, you may receive the following error message:
The directory name is invalid.

CAUSE

You receive the error message because the dump file is actually saved on the remote computer where you are debugging the process. However, the Save Dump As dialog box displays the directory structure as it applies to the computer from where you are remotely debugging. If there is a directory on the remote computer with the same name as the directory that you specified to save the dump file to, the dump file is saved to the directory on the remote computer, instead of on the computer from where you are remotely debugging.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

Steps to reproduce the behavior

The following steps assume that the Remote Debugging Setup is installed and running on the remote computer where you intend to debug a process remotely.
  1. Start Visual Studio .NET.
  2. On the Tools menu, click Debug Processes.
  3. In the Processes dialog box, select TCP/IP (Native only) in the Transport list, and then in the Name box, type the name of the computer where you want to debug a process remotely. Press ENTER (msvcmon must be running on the remote computer where the process is being debugged).
  4. Under Available Processes, click the process that you intend to debug remotely from the list, and then click Attach.
  5. In the Attach to Process dialog box, under Choose the program types that you want to debug, click to select the Native check box. Click OK. The process that you selected appears in the Debugged Processes list.
  6. Click Break, and then click Close.
  7. On the Debug menu, click Save Dump As. In the Save Dump As dialog box, select the directory, and then specify the file name in the File name text box where you want to save the dump file.

    You receive the error message that is described in the "Symptoms" section.
Note To work around the problem, select the directory that is not present on the remote computer where the process is being debugged.

REFERENCES

For more information about how to enable remote debugging on Windows XP Service Pack 2, visit the following Microsoft Developer Network (MSDN) Web site:

Modification Type:MinorLast Reviewed:8/24/2005
Keywords:kbvs2002sp1sweep kbide kbBug KB814794 kbAudDeveloper kbAudITPRO