-
-
Notifications
You must be signed in to change notification settings - Fork 21.5k
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
Show errors from non-main threads in editor #63267
Conversation
Does this solve #2446 ? Edit: I commented before reading the PR, it does not:
|
@akien-mga this PR is me learning the code base around VM and debugger enough to go work on 2446... |
@Faless can I close this? You mentioned elsewhere that you thought it was wrong, but that may have been a misunderstanding. |
Seeing how #76582 is merged, is this still relevant? |
The GDScript VM breaks out of the current function on error, such as assertion failures or general script errors. These errors cause debug breakpoints when running under the debugger/editor. However, threads that are not the main thread are not able to be debugged. For any worker threads, these errors were just printed to stderr, and then the thread would silently exit the current frame, leading to unpredictable results. There was no indication in the Editor itself.
This change submits such errors to the error reporting facility of the debugger also, so they can be displayed in the editor as Errors. They still don't cause debug breakpoints, because that would require general support for thread debugging. This is for notifications only.
Example program: