-
Notifications
You must be signed in to change notification settings - Fork 610
Add error logging to GLFW implementation #241
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
Comments
stuartmorgan-g
added a commit
to stuartmorgan-g/flutter-desktop-embedding
that referenced
this issue
Jan 22, 2019
Add error logging when starting the Flutter engine fails (on all platforms), and on GLFW errors. Also exit early with error logging for unrecoverable errors in the GLFW implementation. Fixes google#241.
stuartmorgan-g
added a commit
to stuartmorgan-g/flutter-desktop-embedding
that referenced
this issue
Jan 22, 2019
Add error logging when starting the Flutter engine fails (on all platforms), and on GLFW errors. Also exit early with error logging for unrecoverable errors in the GLFW implementation. Fixes google#241.
stuartmorgan-g
added a commit
to stuartmorgan-g/flutter-desktop-embedding
that referenced
this issue
Jan 22, 2019
Add error logging when starting the Flutter engine fails (on all platforms), and on GLFW errors. Also exit early with error logging for unrecoverable errors in the GLFW implementation. Fixes google#241.
stuartmorgan-g
pushed a commit
that referenced
this issue
Jan 22, 2019
Add error logging when starting the Flutter engine fails (on all platforms), and on GLFW errors. Also exit early with error logging for unrecoverable errors in the GLFW implementation. Fixes #241.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Both the example embedders and the GLFW embedding implementation itself have error paths that don't do any logging, which makes failures harder to debug than they should be (see #240 for example). All of the error cases should log before returning/exiting.
The text was updated successfully, but these errors were encountered: