You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If XQEMU fails to start, which might be caused by an invalid command line being passed to it (e.g. use controllers which are not connected), XQEMU-Manager will fail to connect to XQEMU over QMP. A cryptic "WinError 10061" error message will be displayed to users. In this case, we should be able to determine why XQEMU failed to start and report this to the user.
Additionally, XQEMU-Manager isn't aware of when the XQEMU subprocess crashes (e.g. hitting an assert), but it should be. We should be able to collect error messages and display them to the users. In the future, automated error reporting would be nice too but that's a separate issue.
The text was updated successfully, but these errors were encountered:
If XQEMU fails to start, which might be caused by an invalid command line being passed to it (e.g. use controllers which are not connected), XQEMU-Manager will fail to connect to XQEMU over QMP. A cryptic "WinError 10061" error message will be displayed to users. In this case, we should be able to determine why XQEMU failed to start and report this to the user.
Additionally, XQEMU-Manager isn't aware of when the XQEMU subprocess crashes (e.g. hitting an assert), but it should be. We should be able to collect error messages and display them to the users. In the future, automated error reporting would be nice too but that's a separate issue.
The text was updated successfully, but these errors were encountered: