-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
Crash without useful error message when no display available #40
Comments
for instance, this can be reproduced when sshing from OSX without the -Y flag. With -Y everything works well. |
oof it seems to take a while to scan when ssh'ing+X11 forwarding over the local networks. Maybe the scanning is sequentially dependent on updating the display, in order to animate the read job decrements? |
Well, it crashes deep within Qt inside the QApplication constructor:
^^^^^^^^^^^^^^^^^^^^^^ crash ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It crashes because Qt itself calls The logger could duplicate the fatal error message to stderr, but that's about all the app can do. In particular, it cannot simply continue. |
Now duplicating a fatal message to stderr, and in the particular case of "Could not connect to display" (and only then) simply calling exit(1), not abort() which dumps core:
|
sshing into my headless server with X window forwarding not set up, I get a crash and core dump because there's no display to attach to. This is stupid and PEBKAC, but maybe this case can be cleaned up to not crash.
The text was updated successfully, but these errors were encountered: