and avoid a very fragile design.
Now I checked that thing and yes, it is definitely a lot better way to
solve the problem. Thanks for clarifying and please just ignore the
patch :)
--
Hannu Lyytinen
Senior Software Developer, Nomovok Ltd
email: hannu.lyyti...
ou really
know what you are doing. You are right it cannot be used carelessly.
--
Hannu Lyytinen
Senior Software Developer, Nomovok Ltd
email: hannu.lyyti...@nomovok.com
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Hello,
we were working on a project which involved nested wayland protocol
requests and bumped into a small re-entrancy issue in
wl_display_iterate(). Basically it is better to check the length
of remaining data on every iteration since the nested request might
have consumed those bytes already.
_
This fixes a possible re-entrancy issue in case of nested requests.
---
src/connection.c |8 +++-
src/wayland-client.c |6 --
src/wayland-private.h |1 +
3 files changed, 12 insertions(+), 3 deletions(-)
diff --git a/src/connection.c b/src/connection.c
index 2795481..c5
