bug in ivi-share.c: crash when touching local and remote
Mizuno, Wataru (ADITJ/SWG)
wmizuno at jp.adit-jv.com
Sun May 14 21:42:02 EDT 2017
Thank you for your response.
>We are using two minnowboards, with our own ivi-share client and remote client.
You connect two minnowboards with Ethernet or something other networks, is it correct?
In that case I have no idea how to share the buffer.
Because in simple-ivi-share the buffer is shared between local application by passing buffer object name.
And also I have a question about how to share the wl_seat between two boards.
Could you tell me more detailed settings about aboves?
ADITJ / SWG
From: florian.haenel [mailto:florian.haenel at lge.com]
Sent: Thursday, May 11, 2017 11:05 PM
To: Mizuno, Wataru (ADITJ/SWG); genivi-ivi-layer-management at lists.genivi.org
Cc: securitycheck at denso.co.jp
Subject: Re: bug in ivi-share.c: crash when touching local and remote
We are using two minnowboards, with our own ivi-share client and remote client.
if I remember correctly the bug manifests when you first touch a surface
on the remote screen, then on the local screen, then release the remote
On 11.05.2017 11:32, Mizuno, Wataru (ADITJ/SWG) wrote:
> Hello Florian,
> I am reviewing your PR and also trying to realize the bug. But I cannot reproduce.
> Could you tell me your environment(board, ivi-extension version...)?
> Best regards,
> Wataru Mizuno
> ADITJ / SWG
> -----Original Message-----
> From: genivi-ivi-layer-management [mailto:genivi-ivi-layer-management-bounces at lists.genivi.org] On Behalf Of florian.haenel
> Sent: Monday, May 8, 2017 8:28 PM
> To: genivi-ivi-layer-management at lists.genivi.org
> Subject: Re: bug in ivi-share.c: crash when touching local and remote
> Maybe the mailing list stripped the attachment from my email.
> PR is here: https://github.com/GENIVI/wayland-ivi-extension/pull/28
> On 08.05.2017 12:40, florian.haenel wrote:
>> Hi all,
>> We found a bug when touching both the local and remote screen in a
>> ivi-share setup.
>> The bug manifests as running through the end of
>> seat->touch_state->resource_list without finding the resource with the
>> right client.
>> This seems to happen because the surface already has focus and is put
>> into touch_state->focus_resource_list instead.
>> after the loop target_resource contains an invalid value. My patch is
>> straightforward, but we can debate what should happen in this case.
>> genivi-ivi-layer-management mailing list
>> genivi-ivi-layer-management at lists.genivi.org
> genivi-ivi-layer-management mailing list genivi-ivi-layer-management at lists.genivi.org
More information about the genivi-ivi-layer-management