bengtmartensson / bengtmartensson/DevSlashLirc

write(2)-errors to /dev/lirc are not transmitted to Java

Open
#14 0 comments 0 reactions 0 assignees View on GitHub
bug help wanted
Dominant language
C++
Stars
4
Forks
4
PR merge metrics
No merged PRs in 30d

Description

JNIEXPORT void JNICALL Java_org_harctoolbox_devslashlirc_Mode2LircDevice_sendNative(....) returns void, may be enough to change to jboolean.

The following signals is too long (?), and fails silently using IrScrutinizer

0000 006C 002A 0000 015B 00AD 0016 0016 0016 0041 0016 0016 0016 0041 0016 0041 0016 0041 0016 0041 0016 0016 0016 0041 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0041 0016 0041 0016 0016 0016 0041 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0016 0016 0016 0016 0041 0016 0041 0016 0041 0016 05F7 015B 0057 0016 0E6C 015B 0057 0016 0E6C 015B 0057 0016 0E6C 015B 0057 0016 0E6C

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the JNI entry point Java_org_harctoolbox_devslashlirc_Mode2LircDevice_sendNative and inspect its Java caller and native write path. Reproduce the supplied long signal through IrScrutinizer, then verify that write(2) failures from /dev/lirc are reported to Java rather than failing silently.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, java, linux
Domain
backend-api-design, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.