Tests failing for ppc64le
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.4k
- Forks
- 252
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 3
Description
Test failing on ppc64le, when i have tested with luajit2-test-suite using luajit
[root@2092f12255fb luajit2-test-suite]# gdb --args luajit test/misc/tonumber_scan.lua
Starting program: /usr/local/bin/luajit test/misc/tonumber_scan.lua
Program received signal SIGSEGV, Segmentation fault.
0x00000000000030e8 in ?? ()
Missing separate debuginfos, use: yum debuginfo-install glibc-2.28-189.5.el8_6.ppc64le libgcc-8.5.0-15.el8.ppc64le
(gdb) bt
#0 0x00000000000030e8 in ?? ()
#1 0x000000001003fcf4 in lj_BC_FUNCC ()
#2 0x000000001001cb68 in lua_pcall (L=0x79600380, nargs=0, nresults=-1, errfunc=2) at lj_api.c:1145
#3 0x0000000010004de8 in docall (L=0x79600380, narg=0, clear=0) at luajit.c:122
#4 0x0000000010005ae4 in handle_script (L=0x79600380, argx=0x7ffffffffb30) at luajit.c:292
#5 0x00000000100069ec in pmain (L=0x79600380) at luajit.c:550
#6 0x000000001003fcf4 in lj_BC_FUNCC ()
#7 0x000000001001cda0 in lua_cpcall (L=0x79600380, func=0x10006808 , ud=0x0) at lj_api.c:1173
#8 0x0000000010006b8c in main (argc=2, argv=0x7ffffffffb28) at luajit.c:581
(gdb) info f 0x00000000000030e8
Stack frame at 0x30e8:
pc = 0x0; saved pc =
Outermost frame: previous frame identical to this frame (corrupt stack?)
Arglist at 0x7ffffffff260, args:
Locals at 0x7ffffffff260, Previous frame's sp is 0x7ffffffff260
(gdb) info f 0x000000001003fcf4
Stack frame at 0x1003fcf4:
pc = 0x0; saved pc =
Outermost frame: previous frame identical to this frame (corrupt stack?)
Arglist at 0x7ffffffff260, args:
Locals at 0x7ffffffff260, Previous frame's sp is 0x7ffffffff260
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
Reproduce the failure with luajit test/misc/tonumber_scan.lua under gdb on ppc64le, starting with the backtrace and the referenced lj_api.c and luajit.c entry points. Trace the SIGSEGV and verify that the test no longer crashes on ppc64le.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100