-
Notifications
You must be signed in to change notification settings - Fork 2
Remote Debugging from Visual Studio
Freddie Akeroyd edited this page Feb 9, 2021
·
9 revisions
Remote debugging allows you to debug in visual studio c and c# applications running on another machine. To do this:
- On the remote machine run the visual studio remote debugging (x64) tool for your version of visual studio. It can be downloaded from microsoft but may be there already. You can also run the one at
ISIS_Experiment_Controls_Public\VS_Remote_Debuggers\VS2017\x64
- Set the tool to allow no authentication (Tools->Options No Authentication)
- Set the environment variable on your local machine
_NT_SYMBOL_PATH=srv*\\isis.cclrc.ac.uk\inst$\Kits$\CompGroup\ICP\Releases\Symbols;srv*\\isis.cclrc.ac.uk\inst$\Kits$\CompGroup\ICP\EPICS\Symbols;srv*\\isis.cclrc.ac.uk\inst$\Kits$\CompGroup\ICP\ISISICP\Symbols;srv*c:\MyServerSymbols*https://msdl.microsoft.com/download/symbols
- Run VS on your local machine
- Select Debug -> Attach to Process
- Set Connection Type Remote(no authentication) and use the server name in connection target
- Select the process from the list
- If you need to catch an error in ioc startup, start the ioc with
runIOC.bat aaa
this will cause it to start up with running st.cmd. - Once you are connected and have break points setup then type
< st.cmd
to boot the ioc
- If you need to catch an error in ioc startup, start the ioc with
- Open the Modules windows (Debug -> Windows -> Modules), find a module you are interested in right click and do load symbols. I am a bit hazy on how this works Freddie knows more. If it works for you please put how you did it here.
- You should now be a able to open code and put breakpoints in as usual.