[ANNOUNCE] libevdev 1.2
Daniel Martin
consume.noise at gmail.com
Wed May 7 01:11:40 PDT 2014
On 7 May 2014 09:41, David Herrmann <dh.herrmann at gmail.com> wrote:
> Hi
>
> On Thu, May 1, 2014 at 4:50 PM, Andreas Radke <a.radke at arcor.de> wrote:
>> I'm getting test failures here:
>>
>>
>> FAIL: test-libevdev
>> ===================
>>
>> Running suite(s): libevdev_has_event tests
>>
>> FAIL: test-kernel
>> =================
>>
>> Running suite(s): kernel tests
>> 0%: Checks: 3, Failures: 0, Errors: 3
>> test-kernel.c:38:E:EVIOCREVOKE:test_revoke:0: (after this point) Received signal 11 (Segmentation fault)
>> test-kernel.c:98:E:EVIOCREVOKE:test_revoke_invalid:0: (after this point) Received signal 11 (Segmentation fault)
>> test-kernel.c:127:E:EVIOCREVOKE:test_revoke_fail_after:0: (after this point) Received signal 11 (Segmentation fault)
>>
>> Rechecked and get the same with libevdev 1.1 here building the package for ArchLinux. Happens with gcc4.8
>> and gcc4.9 toolchain here.
>
> You probably run a pre-3.11 kernel, do you? EVIOCREVOKE isn't
> available there so the tests are meant to fail. I wonder why it fails
> with segfault, though. Can you run the test directly and try to get a
> backtrace? (gdb ./test-kernel)
The segfault happened due to a null dereference and is fixed with
Peters patch "Ignore NULL as argument in libevdev_uinput_destroy()".
With the patch and not having the permission to open the devices the
tests "fail properly" with a permission denied instead of a segfault.
More information about the Input-tools
mailing list