luaL_newstate() return NULL in ppc64le.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.4k
- Forks
- 252
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 3
Description
The environment is ppc64le/UBI 8.3 (RHEL 8.3 based container environment).
In fluent-bit application, luajit2 used as a filter and when creating lua context from application using luaL_newstate() function returns the value NULL instead of lua_state* pointer which causes issue.
This is inconsistent.
Sometimes luaL_newstate() function returns lua_state* pointer.
Sometimes function returns NULL pointer.
Tried on x86_64 for parity check, luaL_newstate() function returns lua_state* pointer always. No failures seen.
Any pointers help would be great.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the luaL_newstate() call in the fluent-bit application and compare behavior on ppc64le/UBI 8.3 with x86_64. Reproduce the intermittent NULL result and inspect the surrounding LuaJIT state-creation path. Done means identifying why ppc64le differs and verifying a consistent non-NULL result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100