Peter Hutterer <[email protected]> writes: > ==26141== Invalid read of size 8 > ==26141== at 0x58FAEA: DeliverEmulatedMotionEvent (exevents.c:1484) > > An InternalEvent is bigger than a DeviceEvent, thus copying one to the other > reads past the allocated boundary. Shouldn't have any real effect since we > shouldn't access anything past the DeviceEvent boundary if the event type is > correct.
How does a DeviceEvent end up getting passed to this function? Is there a cast up the stack somewhere? If DeliverEmulatedMotionEvent actually takes a DeviceEvent cast to an InternalEvent, perhaps the problem is with the signature of DeliverEmulatedMotionEvent? -- [email protected]
pgppO67fwP_bN.pgp
Description: PGP signature
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
