Anyone got remote debug work with VC6.0?

[Jhou]

Hi,

Anyone got remote debug work with vc6.0?

I have read Jon Fincher's article about remote bebug. It mentions both
Visual Studio 6.0 and .NET. But the instructions are for .NET. It seems
that I can connect to remote device using VC.NET. But I cannot get VC6.0 to
connect with same setting of the remote device.

From VC6.0, I select "Network(Tcp/ip)" and "Settings" from "Build->Debugger
remote connection", and set "remote executable path" from Debug setting
page.
When I start debug, vc try to connect to remote machine, but failed with
message of
"VC++ debug monitor is not correctly installed and running on the machine
XXX".
But I know the monitor is running, and I can connect to it using VC.net.

Any suggestion?

Thanks for help.

Jianxin

 

[KM]

Jhou,

Are you running msvcmon.exe on the target from VC 6.0 or from .Net? I mean did you replace the msvcmon.exe on the target by the one
from VC 6.0 when you switched to VC 6.0 Remote Debugging?
The msvcmon has been changed between 6.0 and .Net quite a bit.
The msvcmon version from .Net is 7.10.xxxx, while in VC 6.0 it is version 6.0.xxx. The tool protocol may have been changed.

Also, on the target make sure that msdis100.dll, tln0t.dll and dm.dll are from VC 6.0.

 

[Jack Furr]

You need to copy MSVCMON.EXE and all dependant .DLL files to your remote
machine and run MSVCMON.EXE. This file can be found in the Microsoft Visual
Studio\Common\MSDev98\Bin directory (i.e. C:\Program Files\Microsoft Visual
Studio\Common\MSDev98\Bin)

You may also need to tell your VC project where to find .DLL's that are
compiled or are specific to your project. You'll understand when you debug
your application. You'll be asked where to load your projects .DLL files
from.

You can use depends.exe on MSVCMON.EXE to see the dependant.DLL files.

Jack Furr
Sr. Software Engineer
Netpulse, LLC
http://www.netpulse.com

 

[Jon Fincher]

Hi,

Anyone got remote debug work with vc6.0?

I have read Jon Fincher's article about remote bebug. It mentions both
Visual Studio 6.0 and .NET. But the instructions are for .NET. It
seems that I can connect to remote device using VC.NET. But I cannot
get VC6.0 to connect with same setting of the remote device.

Check out my teammate, Aaron's, blog at http://blogs.msdn.com/astebner.
He's got some good info on debugging, and at least one entry
specifically on debugging that you can view directly at
http://blogs.msdn.com/astebner/archive/2004/07/08/177790.aspx, and if
you scan down his blog, he has some entries on debuggin and development
on XPE. He came ot XPE from the Visual Studio team, so he's the man,
and his blog is worth the read (his blog is better than mine).

 

[Jhou]

Thanks for all the responses, which help me get started.

After copy msvcmon.exe, dm.dll, msdis110.dll, and tlnot.dll from C:\Program
Files\Microsoft Visual Studio\Common\MSDev98\Bin, as suggested from Jack's
response, to the remote device, It seems that I can start the remote debug
from my development machine (xp pro). However I cannot find other
corresponding files such as msvcr60.dll (msvcr71.dll), NatDbgDM.dll, and
NatDbgTLNet.dll for VS6.0. Therefore I leave those .NET dlls in the remote
directory. Where to find those dlls for 6.0. Does it matter?

In this setting, I can start the remote application, and step into some of
the codes. But when I debug into some of other code (at break points), it
crashed my VS6.0 on development machine.

During debug, I have use the system dlls from the local machine, which
cause warnings about mismatch of dlls between local and remote. Does this
matter? Also I have debuged the release version of my application with debug
setting. VS also complains about no debug information for those system dlls
such MFC42.dll.

What is wrong?
Any suggestions?

Thanks

Jianxin

Jhou,

Are you running msvcmon.exe on the target from VC 6.0 or from .Net? I mean

did you replace the msvcmon.exe on the target by the one

from VC 6.0 when you switched to VC 6.0 Remote Debugging?
The msvcmon has been changed between 6.0 and .Net quite a bit.
The msvcmon version from .Net is 7.10.xxxx, while in VC 6.0 it is version

6.0.xxx. The tool protocol may have been changed.