Hi Everyone!
During testing done with Unity’s Default HMI for an embedded platform we encountered a problem:
in a multiscreen configuration (i.e. with Central, Cluster and Passenger on 3 separate screens) the moment the screens are tapped simultaneously on different screens with sequential touches the application crashes producing this error in the Player.log.
Received signal SIGSEGV (11) - code:1 errno:0 addr:0x30
Obtained 18 stack frames.
#0 0x00007f8856756c in (Unknown)
#1 0x00007f8a1225e8 in __kernel_rt_sigreturn
#2 0x00007f80dea710 in wl_proxy_get_user_data
#3 0x00007f892caff0 in (Unknown)
#4 0x00007f80dd02e8 in (Unknown)
#5 0x00007f80dcf828 in (Unknown)
#6 0x00007f80dec9fc in (Unknown)
#7 0x00007f80de8a54 in (Unknown)
#8 0x00007f80dea37c in wl_display_dispatch_queue_pending
#9 0x00007f892c8ce8 in (Unknown)
#10 0x00007f892425c0 in (Unknown)
#11 0x00007f89242684 in (Unknown)
#12 0x00007f8856b090 in (Unknown)
#13 0x00007f886a53cc in (Unknown)
#14 0x00007f88561a60 in PlayerMain(int, char**)
#15 0x00007f869db118 in __libc_start_main
#16 0x0000000021002c in (Unknown)
#17 0x0000000021002c in (Unknown)
I tried to debug the application using gdb to get more information about the crash, but unfortunately the unity executable does not provide debug symbols. Does anyone know if it is possible to enable this functionality in a build for embedded in Unity? It is already in a “Development Build” configuration, but even then it doesn’t work properly.
Regarding the default HMI application provided as an example, it does not seem to be there the problem since with another very simple Multiscreen application with little content inside it, keeping same actions we get the same error.
As far as seen and assumed it would seem that the events between Unity and wayland are not handled properly, by chance is there any way to see in some plugin or extension for embedded some source code for handling touch events on a multi screen setup?
Thank you in advance for your response.