openresty / openresty/luajit2

some test cases can't pass in ARM, but in X86_64 is OK.

Open
#87 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
1.4k
Forks
252
Avg merge
7d 11h
Merged PRs (30d)
3

Description

OS: centos 7.6
ARCH: aarch64(ARM)

LuaJIT compile command:

make TARGET_STRIP=@: CCDEBUG=-g CC=cc XCFLAGS="-DLUA_USE_APICHECK -DLUA_USE_ASSERT -DLUAJIT_NUMMODE=2 -g -O1 -std=gnu99"

only two cases occurs exception:

=== test/ffi/ffi_jit_struct.lua
/DATA/yfli1/test/upngx-test/luajit-test-suite/luajit/bin/luajit-2.1.0-beta3: bad light userdata pointer
stack traceback:
	[C]: in function 'alloc'
	catch_cpp.lua:22: in main chunk
	[C]: at 0x00405004
Failed test when running /DATA/yfli1/test/upngx-test/luajit-test-suite/luajit/bin/luajit-2.1.0-beta3 catch_cpp.lua 1: 256

=== test/misc/catch_wrap.lua
/DATA/yfli1/test/upngx-test/luajit-test-suite/luajit/bin/luajit-2.1.0-beta3: bad light userdata pointer
stack traceback:
	[C]: in function 'wrapon'
	catch_wrap.lua:3: in main chunk
	[C]: at 0x00405004
Failed test when running /DATA/yfli1/test/upngx-test/luajit-test-suite/luajit/bin/luajit-2.1.0-beta3 catch_wrap.lua 1: 256

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the reported failures using the given LuaJIT build command on aarch64: test/ffi/ffi_jit_struct.lua and test/misc/catch_wrap.lua both report "bad light userdata pointer." Compare these cases with an x86_64 run and inspect the referenced test scripts and their stack traces. Done means both ARM cases pass without the exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, lua
Domain
compilers, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.