- #Clion debugger not working install#
- #Clion debugger not working windows 10#
- #Clion debugger not working code#
- #Clion debugger not working windows#
#Clion debugger not working windows#
Configure remote debugging through Windows firewall To allow specific apps through the Windows firewall, see Configure remote debugging through Windows Firewall. Required if your domain policy requires network communication to be performed through IPSec. To debug on a remote IIS web server, open port 80 on the remote computer. If your domain policy requires network communication to be performed through IPSec, you must open additional ports on both the Visual Studio and remote computers. Debugger Managed Compatibility Mode enables a legacy, Visual Studio 2010 version of the debugger. If you select Use Managed Compatibility Mode under Tools > Options > Debugging, open these additional remote debugger ports. (Optional) Required for remote debugger discovery. For more information, see Visual Studio remote debugger port assignments. This port is only used to remote debug a 32-bit process from a 64-bit version of the remote debugger. For more information, see Visual Studio remote debugger port assignments.įor VS 2019 and Azure App Service. The port number increments by 2 for each Visual Studio version. The new rule should appear and be selected in the Inbound Rules or Outbound Rules list.įor Windows Firewall, you can use PowerShell commands such as New-NetFirewallRule.įor VS 2019 and Microsoft Azure App Service. Select one or more network types to enable, including the network type for the remote connection, and then select Next.Īdd a name for the rule (for example, msvsmon, IIS, or Web Deploy), and then select Finish. Select Allow the Connection, and then select Next.
Under Specific local ports, enter a port number from the following tables, and select Next. Select either TCP or UDP, depending on the port number from the following tables. In the New Inbound Rule Wizard, select Port, and then select Next. For an outgoing rule, select Outbound Rules instead. Starting in Windows 10, this is Windows Defender Firewall with Advanced Security.įor a new incoming port, select Inbound Rules and then select New Rule. In Windows Start menu, search for and open Windows Firewall with Advanced Security. However, in some scenarios, such as a third-party firewall, you may need to open ports manually. Visual Studio and the remote debugger try to open the correct ports during installation or startup.
#Clion debugger not working windows 10#
Windows 8/8.1, Windows 10 and newer versions, and Windows Server 2012 settings use the word app, while Windows 7 and Windows Server 2008 use the word program. You can set the appropriate toolchain by running rustup default "toolchain_name".The instructions for configuring the Windows firewall differ slightly on different operating systems, and for older versions of Windows. If you’re on MinGW64, it should be x86_64-pc-windows-gnu. For example, if you’re working on MinGW (32-bit), the default toolchain should be i686-pc-windows-gnu. Then, run rustup toolchain list and check the first line: it should be one of the gnu versions matching the bitness of the debugger. On Windows, go to Settings | Build, Execution, Deployment | Toolchain and set either Cygwin or MinGW as your working environment.
I ended up following this guide by Jetbrains themselves:
#Clion debugger not working install#
Turns out that I'm super dumb and had the Clion pointing at a 32 bit install rather than the 64 bit install. Where as I going wrong? and what is miss configured? Which is where I'm getting the idea that the correct toolchain is being used (as it says x86_64 all over the place). Running rustup show returns this: rustup show (though I don't know enough about rust to be 100% sure) The compiler I added is 64 bit and since I installed the 64 bit version of rust I assume that the programs that it outputs are 64bit. If I google the error I get this issue on github which essentially says use a 64bit compiler on a 64bit app. Though running without debugging works fine.
#Clion debugger not working code#
I'm new to rust and would like to debug my Rust code using Clion (19.3 currently) and followed this answer to switch the compiler from MSVC to GNU, Now when I run my program (in debug) I get this error from Clion: .$GDBCommandException: Error creating process, (error 50).
0 kommentar(er)
