[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 395
  • Last Modified:

remote debugging vs 2005

ok i am new to remote debugging but need to use it as i have several machines that hang randomly and i am trying to find out why.

i am missing something though.

i recompiled with debug info installed all pbp files in the directory my app and am running it on my local machine as a test.
i have started msvmon (i need this right).

i open up visual studio and go to tools and attach to process.

i can attach but can only get assembler symbols.
what do i need to see my source code what am i missing.

thanks in advance greg
0
Autoeforms
Asked:
Autoeforms
  • 4
  • 4
1 Solution
 
Bob LearnedCommented:
Does the remote location have the .pdb file in the same location where the executable is?

Bob
0
 
AutoeformsAuthor Commented:
yes
0
 
Bob LearnedCommented:
Is the project open in the IDE?

Bob
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
AutoeformsAuthor Commented:
ok i was not running the project i was just attaching.

now when i have the project open i get an error message that says the project was built without debug information. is is in fact wrong. i have built and rebuilt the project with debug info.  now what.

the only thing i can think of is the i am running out of directory called bindevl but all the pdb files are there.

any help is greatly appreciated.

greg
0
 
Bob LearnedCommented:
Greg,
What type of project(s) are you trying to remotely debug?

Bob
0
 
AutoeformsAuthor Commented:
vb.net 2005 windows forms.

it is hanging on the task bar occasionally and i want to be able to break it and see where it is stuck

g
0
 
Bob LearnedCommented:
Have you seen this?

Remote Debugging of a Project Built Locally
http://msdn2.microsoft.com/en-us/library/8x6by8d2(vs.80).aspx

To prepare the remote machine
Copy the executable mywin4m.exe to a location on the remote machine (for this example, c:\temp\mywin4m.exe., along with the associated PDB (mywin4m.pdb) and DLLs or other files necessary to run the program.

To prepare the local machine
From the Project menu, choose Properties.

In the mywin4m properties page, click Debug.

For the Start Action setting, select Start external program and in the adjacent text box, enter c:\temp\mywin4m.exe.

Under Start Options, in the Working directory box, enter c:\temp.

Select Use remote machine and enter remote1 in the adjacent text box.

In the Command line arguments box, enter any arguments you want to pass to your application on the remote machine.

If you want to do mixed-mode debugging of managed and unmanaged code, select Enable unmanaged code debugging.

Start the Remote Debugging Monitor on the remote machine. (See How to: Run the Remote Debugging Monitor.)

From the Debug menu, choose Start and begin debugging.

Bob
0
 
AutoeformsAuthor Commented:
have not and will check out.
thanks so much
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now