ASP.NET Core
A set of technologies in the .NET Framework for building web applications and XML web services.
4,803 questions
How I Debug dotnet console app exists on remote linux server from my local windows machine?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 86%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EN%3C/text%3E%3C/svg%3E)
NALB
71
Reputation points
hello ,
I have added my dot net app on Linux and it runs and work the problem that it shucks at some point so I wanna debug it in order to know where is the problem ?
in order for me to do this I followed the steps in this link (https://learn.microsoft.com/en-us/visualstudio/debugger/remote-debugging-dotnet-core-linux-with-ssh?view=vs-2019#build-and-deploy-the-application) at the deployment are i just got all my code and added on the remote Linux server and i build and run it ...
then at the attach process section I was able to connect to server and attach it to botnet however when it starts thee debugger the break point has a warning sign that it can not be hit.
I have searched in that and found that maybe because different versions how ever my dotnet is 6.0.300 and the server's 6.0.405 is that the problem as i have tried to align both versions but it is not working ...
Could you please help me solving this ASAP , Thank you .
ASP.NET Core
C#
C#
An object-oriented and type-safe programming language that has its roots in the C family of languages and includes support for component-oriented programming.
11,339 questions
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 90%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EZL%3C/text%3E%3C/svg%3E)
Zhi Lv - MSFT 33,166 Reputation points Microsoft External Staff2023-02-23T02:43:01.9033333+00:00 Hi @NALB
To the Breakpoint Warnings, you can hover over the breakpoint and see if there's a warning. The following two sections describe prominent warnings and how to fix them.
- "No Symbols have been loaded for this document"
Go to the Modules window (Debug > Windows > Modules) and check whether your module is loaded.
- If your module is loaded, check the Symbol Status column to see whether symbols have been loaded.
- If symbols aren't loaded, check the symbol status to diagnose the issue. From the context menu on a module in the Modules window, select Symbol Load Information... to see where the debugger looked to try and load symbols. For more information about loading symbols, see Specify Symbol (.pdb) and Source Files.
- If symbols are loaded, the PDB doesn't contain information about your source files. A few possible causes are:
- If your source files were recently added, confirm that an up-to-date version of the module is being loaded.
- It's possible to create stripped PDBs using the /PDBSTRIPPED linker option. Stripped PDBs don't contain source file information. Confirm you're working with a full PDB and not a stripped PDB.
- The PDB file is partially corrupted. Delete the file and run a clean build of the module to try to resolve the issue.
- If your module isn't loaded, check the following to find the cause:
- Confirm that you're debugging the right process.
- Check to see that you're debugging the right code. You can find out what type of code the debugger is configured to debug in the Processes window (Debug > Windows > Processes). For example, if you're trying to debug C# code, confirm that your debugger is configured for the appropriate type and version of .NET (for example, Managed (v4*) versus Managed (v2*/v3*) versus Managed (CoreCLR)).
- If your module is loaded, check the Symbol Status column to see whether symbols have been loaded.
- "… the current source code is different from the version built into..." If a source file has changed and the source no longer matches the code you're debugging, the debugger won't set breakpoints in the code by default. Normally, this problem happens when a source file is changed, but the source code wasn't rebuilt. To fix this issue, rebuild the project. If the build system thinks the project is already up-to-date even though it isn't, you can force the project system to rebuild. Rebuild the project either by saving the source file again or by cleaning the build output before building.
More detailed information, see Troubleshoot Breakpoints in the Visual Studio Debugger
Best regards,
Dillion - "No Symbols have been loaded for this document"
Go to the Modules window (Debug > Windows > Modules) and check whether your module is loaded.
-
NALB 71 Reputation points
2023-02-23T11:14:17.41+00:00 I have small question regarding a point in this line (https://learn.microsoft.com/en-us/visualstudio/debugger/remote-debugging-dotnet-core-linux-with-ssh?view=vs-2019#build-and-deploy-the-application) in the second point if i copied the bin folder which has the dlls and pdbs and paste them on the liux remote server do I need to run any commands in order to start it ? as if I did nothing it won't be seen in the attach process? or is it under different name ?
If I used first solution and took all the code to server , if I built it on the remote server I can see it in the processes to attach but this is not the best for me .
-
Zhi Lv - MSFT 33,166 Reputation points Microsoft External Staff
2023-02-27T07:48:41.7366667+00:00 From the document, we can see that after copy sources to the linux computer, we need to build the application and start the application:
You can use several methods to deploy the app prior to debugging. For example, you can:
- Copy sources to the target computer and build with
dotnet buildon the Linux machine. - Build the app on Windows, and then transfer the build artifacts to the Linux machine. (The build artifacts consist of the application itself, the portable PDBs, any runtime libraries it might depend on, and the .deps.json file.)
When the app is deployed, start the application.
- Copy sources to the target computer and build with
Sign in to comment
Sign in to answer