Hello Nick,
Thanks for your post. As I understand, you configured remote debugging on a
remote Windows NT 4 workstation. Then you copied the execute file and its
corresponding .PDB files, and execute it in the remote system. You are able
to attach the remote process in the local VS .NET, however, it will not hit
any breakpoints you set. Please correct me if there is any
misunderstanding. Now I'd like to share the following information with you:
1. Please make sure that we choose proper program types when attaching to a
process. Though I am do not know the type of your Visual C++ project, I
believe that selecting both "Common Language Runtime" and "Native" will not
go wrong.
2. Another issue may be that Visual Studio .NET pickes up the wrong .pdb
files for your program. Generally speaking, Visual Studio .NET will load
the .pdb files on local instead of on the remote machine. Please check
whether you copied the correct PDB fils to the local machine, and are there
any other copies of that .pdb on your machine (ie in the system32
directory)?
If you build the project locally, I suggest that you can open the project
in Visual Studio .NET IDE before attaching to its remote process.
3. In addition, I am not familiar with VNC. When you connect to a remote
machina via VNC, will it start another user's Terminal Server session? If
so, you will need to apply the remoting debugging settings per MSDN article
below:
Remote Debugging Under Another User Account
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/htm
l/vxtskremotedebuggingacrossmachineaccounts.asp
4. I believe the following article is also helpful:
Setting Up Remote Debugging
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/htm
l/vxtskremotedebuggingacrossmachineaccounts.asp
I am standing by for your response.
Have a nice day!
Regards,
HuangTM
Microsoft Online Partner Support
MCSE/MCSD
Get Secure! --
www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.