* Re: Illegal Instruction in LuaJIT:i686
2021-11-18 0:12 [ISSUE] Illegal Instruction in LuaJIT:i686 tbsteinb
@ 2021-11-18 0:19 ` ericonr
2021-11-18 0:19 ` ericonr
` (6 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: ericonr @ 2021-11-18 0:19 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/34124#issuecomment-972365101
Comment:
You want literally `-p pkgver`, not to replace the known pkgver ;)
> (hoping that building it natively may bypass some obscure bug or something)
i686 packages are built natively.
> I'm not particularly experienced with xbps-src so I left it there, otherwise I would have tried building a debug release and seeing if I could trace the instruction further.
Reinstall `LuaJIT` from official repos, then `void-repo-debug`, then `xbps-install -S LuaJIT-dbg` (and possible `neovim-dbg`, for extra info).
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Illegal Instruction in LuaJIT:i686
2021-11-18 0:12 [ISSUE] Illegal Instruction in LuaJIT:i686 tbsteinb
2021-11-18 0:19 ` ericonr
@ 2021-11-18 0:19 ` ericonr
2021-11-18 0:20 ` ericonr
` (5 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: ericonr @ 2021-11-18 0:19 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/34124#issuecomment-972365101
Comment:
You want literally `-p pkgver`, not to replace the known pkgver ;)
> (hoping that building it natively may bypass some obscure bug or something)
i686 packages are built natively.
> I'm not particularly experienced with xbps-src so I left it there, otherwise I would have tried building a debug release and seeing if I could trace the instruction further.
Reinstall `LuaJIT` from official repos, then `void-repo-debug`, then `xbps-install -S LuaJIT-dbg` (and possibly `neovim-dbg`, for extra info).
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Illegal Instruction in LuaJIT:i686
2021-11-18 0:12 [ISSUE] Illegal Instruction in LuaJIT:i686 tbsteinb
2021-11-18 0:19 ` ericonr
2021-11-18 0:19 ` ericonr
@ 2021-11-18 0:20 ` ericonr
2021-11-18 0:21 ` tbsteinb
` (4 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: ericonr @ 2021-11-18 0:20 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 216 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/34124#issuecomment-972365984
Comment:
That said this looks like Pentium III and I'm not sure we support that :/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Illegal Instruction in LuaJIT:i686
2021-11-18 0:12 [ISSUE] Illegal Instruction in LuaJIT:i686 tbsteinb
` (2 preceding siblings ...)
2021-11-18 0:20 ` ericonr
@ 2021-11-18 0:21 ` tbsteinb
2021-11-18 0:24 ` tbsteinb
` (3 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: tbsteinb @ 2021-11-18 0:21 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 345 bytes --]
New comment by tbsteinb on void-packages repository
https://github.com/void-linux/void-packages/issues/34124#issuecomment-972366608
Comment:
Haha whoops, makes sense. I'll update my post accordingly.
And I wouldn't be surprised if that's the case. This is a really old system. It's too old for OpenBSD, which was a bit of a shocker for me.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Illegal Instruction in LuaJIT:i686
2021-11-18 0:12 [ISSUE] Illegal Instruction in LuaJIT:i686 tbsteinb
` (3 preceding siblings ...)
2021-11-18 0:21 ` tbsteinb
@ 2021-11-18 0:24 ` tbsteinb
2021-11-18 0:31 ` [ISSUE] [CLOSED] " tbsteinb
` (2 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: tbsteinb @ 2021-11-18 0:24 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 270 bytes --]
New comment by tbsteinb on void-packages repository
https://github.com/void-linux/void-packages/issues/34124#issuecomment-972368261
Comment:
You were spot on, it's a Pentium III. I inherited the server so wanted to make sure the CPU didn't get replaced at some point.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [ISSUE] [CLOSED] Illegal Instruction in LuaJIT:i686
2021-11-18 0:12 [ISSUE] Illegal Instruction in LuaJIT:i686 tbsteinb
` (4 preceding siblings ...)
2021-11-18 0:24 ` tbsteinb
@ 2021-11-18 0:31 ` tbsteinb
2021-11-18 0:31 ` tbsteinb
2021-11-18 1:14 ` ericonr
7 siblings, 0 replies; 9+ messages in thread
From: tbsteinb @ 2021-11-18 0:31 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1908 bytes --]
Closed issue by tbsteinb on void-packages repository
https://github.com/void-linux/void-packages/issues/34124
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
Compaq ProLiant DL360 G2
* xuname:
Void 5.13.19_1 i686 GenuineIntel uptodate rFFF
* package:
`LuaJIT-2.1.0beta3_2`
### Expected behavior
Program utilizing LuaJIT runs and can be used successfully
### Actual behavior
A program using LuaJIT crashes with an illegal instruction immediately.
### Steps to reproduce the behavior
I noticed this behavior on neovim, but traced the error to LuaJIT. I suspect other programs using it will fail with the same problem.
The simplest way is to just run `nvim --version`, it will display version info but then give an illegal instruction error. Alternatively, you can launch the editor and then try to do anything (insert mode, or even just moving the cursor is enough) and it will immediately crash with the same error.
### Debugging by me
I got a core dump from neovim and stepped through it to find the error occurs within LuaJIT. I got the following as the source of the illegal instruction:
`#0 0xb7d3100b in lua_pushvalue () from /usr/lib32/libluajit-5.1.so.2`
I attempted to build the package locally via xbps-src (hoping that building it natively may bypass some obscure bug or something), but unfortunately the local build gives the same crash. I'm not particularly experienced with xbps-src so I left it there, otherwise I would have tried building a debug release and seeing if I could trace the instruction further.
Let me know if you need any further information, I'll be glad to submit it.
[luajit-coredump.tar.gz](https://github.com/void-linux/void-packages/files/7558797/luajit-coredump.tar.gz)
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Illegal Instruction in LuaJIT:i686
2021-11-18 0:12 [ISSUE] Illegal Instruction in LuaJIT:i686 tbsteinb
` (5 preceding siblings ...)
2021-11-18 0:31 ` [ISSUE] [CLOSED] " tbsteinb
@ 2021-11-18 0:31 ` tbsteinb
2021-11-18 1:14 ` ericonr
7 siblings, 0 replies; 9+ messages in thread
From: tbsteinb @ 2021-11-18 0:31 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 442 bytes --]
New comment by tbsteinb on void-packages repository
https://github.com/void-linux/void-packages/issues/34124#issuecomment-972372819
Comment:
And yeah, unfortunately you are right. Looks like Pentium 4 is the minimum requirements.
Kind of funny to be honest, if I hadn't encountered this bug I'd have never known I was running on unsupported hardware. Just goes to show how well written the coreutils and Linux are. I'll close the issue.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Illegal Instruction in LuaJIT:i686
2021-11-18 0:12 [ISSUE] Illegal Instruction in LuaJIT:i686 tbsteinb
` (6 preceding siblings ...)
2021-11-18 0:31 ` tbsteinb
@ 2021-11-18 1:14 ` ericonr
7 siblings, 0 replies; 9+ messages in thread
From: ericonr @ 2021-11-18 1:14 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 259 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/34124#issuecomment-972396206
Comment:
No worries :)
If you'd like, you're free to keep using it, just be aware that things might be randomly broken :P
^ permalink raw reply [flat|nested] 9+ messages in thread