-
Notifications
You must be signed in to change notification settings - Fork 544
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
How to remove "Waiting for debugger connection..." Screen? #2654
Comments
Disable debugging in project properties |
Are you talking about Remote Debugging? If you're talking about him, then I turned it off |
and the "Waiting for debugger connection..." message still appears? |
I also told in the question that I disabled this function, if the screen disappeared, I would not ask this question |
I found a solution, in the project settings in the "Profile" in the "Launch" parameter, I set VMware instead of the ISO image, and it all worked |
Oh sorry then lol |
Area of Cosmos - What area of Cosmos are we dealing with?
Creating an iso
Expected Behaviour - What do you think that should happen?
The operating system should not display a "Waiting for debugger connection..." screen upon startup.
Actual Behaviour - What unexpectedly happens?
The "Waiting for debugger connection..." screen is not necessary for me.
Reproduction - How did you get this error to appear?
I wanted to build a standalone operating system in C# using COSMOS, but I was unable to build the Release version due to the error shown in this screenshot: https://prnt.sc/J4ArQTK85B2p The Debug version cannot function independently because it requires a debugger connection, as shown here: https://prnt.sc/TFolxc1m-i-w I found a similar issue here: #1096, but the solution provided there did not work for me because I have already disabled remote debugging, as shown in this screenshot: https://prnt.sc/-5LsApzEbBNP
Version - Were you using the User Kit or Dev Kit? And what User Kit version or Dev Kit commit (Cosmos, IL2CPU, X#)?
I use CosmosUserKit-20221121-vs2022 and Visual Studio 2022
The text was updated successfully, but these errors were encountered: