-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows debugging WSL #6
Comments
Just did some reading on this. This might be a solution, have to try it first though after my local WSL install gets un-stuck on mysterious errors. |
Alright, spent quite some time on this yesterday/today on three different devices, ran into different errors left and right, but at least managed to get wsl to run on two, one just refused. Still, the WSLg variant (with graphical processing, able to launch GUI apps like chrome for us) doesn't work on any. I have a feeling it works semi-natively on Windows 11 though, at least they say so, that it's easier to access, but I really don't want to upgrade. Also, it really blows up the instruction scope and exception handling list, and I fear this would make it flat out inaccessible to your average joe with Windows. Do you think there's any way to make it run on Windows natively? |
With the weekend here, I've decided to bite the bullet and upgrade to Windows 11 in hopes of getting this to run on the new WSLg (which should have run on Win10 in some capacity already but refused in more ways than one.) |
Hey James,
I was testing it out on Windows and I cannot make it work. Tried with 1.2.0 so far but this issue might be version independent:
It looks as if WSL cannot interact with Chrome running outside of WSL, which sort of makes sense, for a subsystem that is but a command line.
I documented the steps that got me here, just so we can add them to the Readme once we get it running (should we, using this approach):
Thanks for your help,
sivanmu
The text was updated successfully, but these errors were encountered: