aboutsummaryrefslogtreecommitdiffstats
path: root/src/scanner.c
diff options
context:
space:
mode:
authorJonas Ådahl <jadahl@gmail.com>2015-12-28 14:33:36 +0800
committerJonas Ådahl <jadahl@gmail.com>2016-01-16 16:37:37 +0800
commitc6437817dd9bbb2fd1027a103e77e238ad5e5ddb (patch)
treeac7a72599a7b6140d33117f01c24611eb987fdaa /src/scanner.c
parenttests: Pass argument to client main (diff)
downloadwayland-c6437817dd9bbb2fd1027a103e77e238ad5e5ddb.tar
wayland-c6437817dd9bbb2fd1027a103e77e238ad5e5ddb.tar.gz
wayland-c6437817dd9bbb2fd1027a103e77e238ad5e5ddb.tar.bz2
wayland-c6437817dd9bbb2fd1027a103e77e238ad5e5ddb.tar.lz
wayland-c6437817dd9bbb2fd1027a103e77e238ad5e5ddb.tar.xz
wayland-c6437817dd9bbb2fd1027a103e77e238ad5e5ddb.tar.zst
wayland-c6437817dd9bbb2fd1027a103e77e238ad5e5ddb.zip
tests: Test that one can fetch the protocol error after EPIPE
If a client is terminated due to some reason, it should always be possible to retrieve protocol error associated with the termination. Test that, while either using the dispatch helpers (wl_display_dispatch(_queue)() or the prepare read API, it should be possible to retrieve the error after EPIPE. Signed-off-by: Jonas Ådahl <jadahl@gmail.com> Reviewed-by: Daniel Stone <daniels@collabora.com>
Diffstat (limited to 'src/scanner.c')
0 files changed, 0 insertions, 0 deletions