![]() I also found some discussions, which are maybe about the same subject, and I tried everything out that I could and found there, but without any luck. ![]() VSCode is launched from within WSL2 by running code. Visual Studio Code is the latest 1.45.1 stable release and includes the WSL remote development extension (0.44.2) on Windows 10. Terminal 1.x is installed and used to access the Linux commandline. The following packages must be present: libfuse2 libxi6. Windows 10 has WSL2 running Ubuntu 20.04. Note, that the debugger seems to be still up, since the process dlv is still there and I can cancel the debugging (it's just simply hanging without even starting the debugging):Īnd these are my Go environment variables: com/issue/ALL-2137 Compile and run Go code using WSL 2 and GoLand. In the dialog that opens, click Sign commits with GPG key and select the key you want to use from the list. In the Settings dialog ( Ctrl Alt 0S ), go to Version Control Git, and click the Configure GPG Key button. Go build, go run and even go install works fine, but debugging hangs shortly after the debugger started showing me this output:Īnd within the run/debug configuration, that's my target: Start GoLand (or restart it to make sure it loads the changes youve made to your environment). There are numerous issue tickets on WSL github about performance. My entire rationale for using WSL1 (and WSL in general) is shared development of a common code base, and right now both subsystem versions have significant problems doing that. Copy your project into wsl internal file system if you need. I might try to switch over to WSL2 until this is fixed, but WSL2 has it's own problems with abysmal shared filesystem performance. My Go source files are on my Windows host system, the GO SDK is installed in both the Windows host and the WSL subsystem. This Microsoft documentation explains that Wsl2 is slower for cross platform file system usage than wsl1. What I am struggeling with (since days now), is to debug go code using the IDE GoLand and using their feature of Run Targets, which is set to WSL 2. Press the Win key to search for XLaunch, make sure the following parameters are present when configuring it: 3. ![]() from the Windows host) using Run Target set to WSL2. That's a question that goes hand in hand with this one here.ĭifference: in the linked question I am using GoLand from within WSL (having Run Target set to its default which is "Local Machine") and in this question I am using GoLand from outside WSL (i.e. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |