Immediate-Mode-UI / Immediate-Mode-UI/Nuklear

Errors Reported By Facebook Infer

Open
#585 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
11.4k
Forks
686
Avg merge
4d 1h
Merged PRs (30d)
3

Description

[inferNuk.zip](https://github.com/Immediate-Mode-UI/Nuklear/files/13274430/inferNuk.zip)

Facebook Infer seems to have found potential errors in Nuklear, including 3 buffer overruns and some unsigned integer overflows and uninitialized values. Would the overflows cause unexpected behaviour? If so, perhaps an overflow blocking header (such as https://mega.nz/file/SxYgzYYQ#7mL1bPyyATYbSTdxi6F7co-QZ63wNtGh2TdP36Gya3g - although it would presumably need to be altered for compatibility with C89) can be used? As for the buffer overruns, could they affect memory safety? The Infer report, and the C files, command line text and makefile involved, are in the Zip file attached to this message (I used Nuklear+ with a small change that allows writing a single event loop for the program, instead of a callback, when running in Emscripten).

Contributor guide

Open the contributing guide

Research direction

Start by unpacking inferNuk.zip and reviewing the Facebook Infer report alongside the included C files, command-line text, and makefile. Verify whether the three buffer overruns, unsigned-integer overflows, and uninitialized values are real, then document or address each confirmed finding and report what behavior or memory-safety impact remains.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend, security
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.