ecore_wl2: Don't treat EINVAL as a recoverable condition

EINVAL is bad, we can't go on.  If we treat it like it's not a fatal
error we'll end up spinning on the fd and constantly retrying sends
on the dead wayland connection.

@fix
This commit is contained in:
Derek Foreman 2016-03-10 13:56:24 -06:00 committed by Chris Michael
parent 358a204491
commit 9646f8e9ec
1 changed files with 3 additions and 3 deletions

View File

@ -235,7 +235,7 @@ _cb_connect_data(void *data, Ecore_Fd_Handler *hdl)
if (ecore_main_fd_handler_active_get(hdl, ECORE_FD_READ))
{
ret = wl_display_dispatch(ewd->wl.display);
if ((ret < 0) && ((errno != EAGAIN) && (errno != EINVAL)))
if ((ret < 0) && (errno != EAGAIN))
{
ERR("Received Fatal Error on Wayland Display");
@ -252,7 +252,7 @@ _cb_connect_data(void *data, Ecore_Fd_Handler *hdl)
if (ret == 0)
ecore_main_fd_handler_active_set(hdl, ECORE_FD_READ);
if ((ret < 0) && ((errno != EAGAIN) && (errno != EINVAL)))
if ((ret < 0) && (errno != EAGAIN))
{
ERR("Received Fatal Error on Wayland Display");
@ -303,7 +303,7 @@ _cb_connect_idle(void *data)
return ECORE_CALLBACK_RENEW;
err:
if ((ret < 0) && ((errno != EAGAIN) && (errno != EINVAL)))
if ((ret < 0) && (errno != EAGAIN))
{
ERR("Wayland Socket Error: %s", strerror(errno));