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
Arch: Debugging just stops when trying to print out "Hello World!" #2819
Comments
Can you enable logging and see what gets printed? |
Sure will do when I get home from work in 8-10 hours |
Enabling the logging didn't seem to do anything. The log file either never got created or I just couldn't find it. Although I did try to set the directory and file name but still, no file was created. What fixed it for me was a solution from a different issue :
edit: extension not plugin |
Glad you figured it out! |
I did the steps jchand99 mentioned but didn't solve it for me, I still can't print out when running a simple hello world console app.
|
@CTJansson are you using a version of VS Code which was built by someone other than Microsoft? (non-official copy) |
Do you have the package "msbuild-stable" installed @CTJansson? I've had issues in some projects when that package isn't installed. |
The issue that @CTJansson is running into is this -- This either means that @CTJansson is using an unofficial version of VS Code, or VS Code is failing to process this request. |
@gregg-miskelly well, it seems I did, I installed the one from arch repository (this is the one causing problems), checked if AUR had a package and sure it did, that one works, so the issue can be closed again. |
(archlinux packager here) Yeah, I am sorry but we are sane people so we run vscode with the electron already installed on your system, we don't package a new copy of electron specifically to run vscode (electron is huge btw). I already had a conversation with the upstream but they won't fix it, because they don't want, really. I guess it bothers them to much to spend a few hours tracking down here they are mishandling the spawning of new instances. Please open an issue with vscode's upstream, if people don't bother them this won't ever get fixed. This is what it looks when Microsoft opensources something. |
@FFY00, I'd love to use the arch packaged vscode, not the Microsoft packaged one in AUR. If for nothing else, for the updates. What is the exact thing stopping vsdbg from working with arch packaged vscode? I thought it was https://aka.ms/VSCode-DotNet-DbgLicense. But please correct me if I'm wrong. |
I explain the reason it doesn't work in the comment above. |
Does it really not work because arch uses the system electron instead of the bundled one? That sounds unlikely. To me, it sounds more likely that Microsoft signs something in their own vscode releases, so that vsdbg can detect whether it's "authentic" or not. Or some similar method. |
VS Code doesn't handle respawns properly when called using the electron binary. If you want to try it yourself you can confirm it is working by compiling vscode yourself. Microsoft is not being stuborn, they are just ignoring the community because that doesn't give them instant PR publicity. |
Oh, thanks for the explanation. I misunderstood, I was talking about a different issue, my bad. |
Environment data
dotnet --info:
VS Code version:
C# Extension version:
1.17.1
Steps to reproduce
i. Worth to mention, running dotnet build and dotnet run works without problems
Expected behavior
Starts debugger and Print out "Hello world" in the debug console
Actual behavior
After the preLaunchTask, the debugger just stops without any error output and not printing "Hello World!" in the debug console.
The text was updated successfully, but these errors were encountered: