9
votes

1) Make an Windows account on Host Machine. Log In.

2) Make an Windows account, with same user name and password as Host Machine, on the Remote Machine. Log In.

3) Copy all .pdb files to same directory as .exe on the Remote Machine.

4) Run Remote Debugger on the Remote Machine.

5) Tools -> Options

6) Radio Button to "No Authentication (native only)" and Check "Allow any user to debug", OK.

7) Run the .exe (debug build) on the Remote Machine.

8) On the Host Machine, open your solution.

9) Debug -> Attach To Process

10) Transport : Remote ( Native only with no authentication )

11) Qualifier : Server IP

12) Refresh

13) Choose the application to debug.

14) Attach

application seems to be running in the visual studio but all the breakpoints grey out with the following comment :

breakpoint will not currently be hit. No symbols have been loaded for this document

I did the folowing I deploy my applicatiob (including the pdb files) in the remote pc under c:\abc I add the symbols location as you can see in the screenshot and I try to debug from my pc to the remote pc butstill no breackpoint

enter image description here Any Idea?

2
You might have solved it now. But here is a nice recipe: codewut.de/content/visual-studio-and-remote-debugging-easy-way – Morten Frederiksen
You should be completely sure that sources and PDBs are in sync in both ends. – synhershko

2 Answers

5
votes

When remotely debugging native code, your symbols must be on the machine with Visual Studio, not on the remote machine.

To let VS find the symbols, just add a folder containing the symbols to your symbol path. Go Tools > Options > Debugging > Symbols, and add the folder to the list.

1
votes

it seems that if you used native you cannt debug c# .net application