Remote debug - Vista target computer

Remote debug - Vista target computer

Post by Sid Pric » Fri, 13 Jun 2008 02:23:20


Hello,
I am trying to get remote debugging operating for my applications.
The build computer is XP Pro SP2, the target computer is Vista Ultimate
running in a VMWare virtual PC on the same XP Pro SP2 computer. These
computers are in the same workgroup and the same user is logged on to both
with the same password.
The application is a managed application and class libraries built and
debugged using VS2005.
I have a connection established to the target and the application (main
project and class libraries) builds onto the target.
I have run "caspol security -off " on the target and I am still getting some
kind of security exception:

First-chance exception at 0x75ea42eb in CueAssist.exe: Microsoft C++
exception: [rethrow] at memory location 0x00000000..
A first chance exception of type 'System.IO.FileLoadException' occurred in
CueAssist.exe

An unhandled exception of type 'System.IO.FileLoadException' occurred in
CueAssist.exe

Additional information: Unverifiable code failed policy check. (Exception
from HRESULT: 0x80131402)

I would really appreciate some pointers here, thank you,

Sid.
 
 
 

Remote debug - Vista target computer

Post by Sid Pric » Sat, 14 Jun 2008 23:03:32


Does nobody have any suggestions here please? Even a suggestion of another
list to pose the question to would be useful.
Thank you,
Sid.

 
 
 

Remote debug - Vista target computer

Post by ZHBz » Wed, 02 Jul 2008 05:57:02

I'm just trying to cope with a similar situation. I've been remote debugging
XP Home target machines from an XP Pro VisualStudio 2005 development machine,
for over a year. Now I'm trying to remote debug on a Vista Home target
machine and I'm running into non-stop headaches.

This post from a msdn forum contains info from some guys at microsoft.
Their last word on the subject was that you can only debug a Vista target
from a Vista dev machine. And you can't ever remote debug on Vista Home.
I'm still searching.

http://www.yqcomputer.com/
 
 
 

Remote debug - Vista target computer

Post by Sid Pric » Wed, 02 Jul 2008 23:18:42


Thank you for this information, however as I read the thread you linked to
the problem is that remote debugging is not supported for Vista Home, either
for the VS or remote machine.
My problems are related to using Vista Ultimate as the remote target, this
should work and I just can't get it working. As far as I know there is no
requirement for having a Vista VS machine to debug a Vista target.
Sid.
 
 
 

Remote debug - Vista target computer

Post by ZHBz » Thu, 03 Jul 2008 05:04:02

I got remote debugging working on Vista Home Basic, Service Pack 1 (SP1).
The development machine is XP Pro Service Pack 2, using Visual Studio 2005
(VS2005).

I needed this post to provide the last bit of information:
http://www.yqcomputer.com/

In the end, I ran a batch file containing the four command lines contained
in the post above, then I just used the msvmon that I had been using.
 
 
 

Remote debug - Vista target computer

Post by Sid Pric » Thu, 03 Jul 2008 07:52:07


I am pleased you got it working, unfortunately this is not the problem I
have since I have the firewall turned off.
Thanks for posting the information, I appreciate your help,
Sid.
 
 
 

Remote debug - Vista target computer

Post by Sid Pric » Wed, 16 Jul 2008 09:41:31

I do not have a resolution to my issue of remote debugging on a Vista
Ultimate target. As I explained earlier I have used caspol -security off to
disable security so that I can debug my application, however doing this
causes another security issue with the following exception:

First-chance exception at 0x75ea42eb in CueAssist.exe: Microsoft C++
exception: [rethrow] at memory location 0x00000000..
A first chance exception of type 'System.IO.FileLoadException' occurred in
CueAssist.exe

An unhandled exception of type 'System.IO.FileLoadException' occurred in
CueAssist.exe

Additional information: Unverifiable code failed policy check. (Exception
from HRESULT: 0x80131402)

I really need to debug this application running under Vista and installing
VS 2005 on the Vista machine is just not an option.

Thanks,
Sid.
 
 
 

Remote debug - Vista target computer

Post by David Chin » Fri, 01 Aug 2008 05:14:30

Sid, can you run the app on the Vista machine without the de *** ? If I
attempt to run my .NET app from a network drive, it throws an exception
(don't know which one). I have to copy the app to the machine I want it
debugged on in order to get around security problems. Maybe this is your
issue, since the when you run it under the de *** , it is as if you are
running the program on a nework drive from the Vista PC's point of view. So
maybe instead you could copy it to the Vista machine and set up the IDE
remote debugging to to run it from there.

Another option is to insert Debug.Assert (false) at the place you want to
debug and run it normally. Then when the assertion is hit, you can attach
the remote de *** at that time.

-- David




Another option is to insert Debug.Assert (false) at the place you want to
debug and run it normally. Then when the assertion is hit, you can attach
the remote de *** at that time.

-- David
 
 
 

Remote debug - Vista target computer

Post by Sid Pric » Mon, 04 Aug 2008 00:19:57


David, this is not the scenario. VS is set to build the EXe and DLLs on the
Vista Machine.

I had to find a way around this issue quickly so I built a Vista machine in
order to do my testing and debug. I did this to eliminate the possibility
that the problems were caused by the VMWare virtual PC environment. It
proved not to be the issue with the same problem happening on the real Vista
machine when using remote debug.
The application would not run under Vista so running it and then attaching
the de *** was not an option since by the time one tried to attach to the
running process it had crashed.
In the end I contacted MS tech supoprt and with their help reconfigured VS
on the XP machine. The changes were in the settings for the debug mode, i.e.
the way the paths to the remote application were set. This resolved my issue
and I have been working on the project for a couple of weeks now with no
further issues.
Thanks for taking the time to respond, I always appreciate input,
Sid.