libinput/test/valgrind.suppressions
Peter Hutterer 1e89ceb93c evdev: recover from a lost button count
If the kernel sends us a button press for a button that is thought to be down
we have lost track of the state of the button. Ignore the button press event,
in the hope that the next release makes things right again.

A release event may be masked if another process grabs the device for some
period of time, e.g. libinput debug-events --grab.

https://bugs.freedesktop.org/show_bug.cgi?id=101796

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
(cherry picked from commit 399c50dbeb)
2017-09-06 19:38:41 +10:00

54 lines
830 B
Text

{
srunner_run::timer_create-uninitialized-bytes
Memcheck:Param
timer_create(evp)
fun:timer_create@@GLIBC_2.3.3
fun:srunner_run
fun:litest_run
fun:main
}
{
mtdev:conditional_jumps_uninitialized_value
Memcheck:Cond
...
fun:mtdev_put_event
}
{
<g_type_register_static>
Memcheck:Leak
...
fun:g_type_register_static
}
{
<g_type_register_static>
Memcheck:Leak
...
fun:g_type_register_fundamental
}
{
<g_type_register_static>
Memcheck:Leak
...
fun:g_malloc0
}
{
libunwind:msync_uninitialized_bytes
Memcheck:Param
msync(start)
fun:__msync_nocancel
...
fun:litest_backtrace
}
{
python:PyUnicode_New
Memcheck:Leak
...
obj:/usr/lib*/libpython3*.so*
}
{
libevdev:grab
Memcheck:Param
ioctl(generic)
fun:ioctl
fun:libevdev_grab
}