Github messages for voidlinux
 help / color / mirror / Atom feed
From: tbsteinb <tbsteinb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Illegal Instruction in LuaJIT:i686
Date: Thu, 18 Nov 2021 01:12:55 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34124@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2089 bytes --]

New 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:  
  I entered `xbps-query -p LuaJIT-2.1.0beta3_2 LuaJIT` but it does not return any results. If someone spots what I'm doing wrong I'll edit this post with the output from the corrected version of the command.

### 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)



             reply	other threads:[~2021-11-18  0:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18  0:12 tbsteinb [this message]
2021-11-18  0:19 ` ericonr
2021-11-18  0:19 ` ericonr
2021-11-18  0:20 ` ericonr
2021-11-18  0:21 ` tbsteinb
2021-11-18  0:24 ` tbsteinb
2021-11-18  0:31 ` [ISSUE] [CLOSED] " tbsteinb
2021-11-18  0:31 ` tbsteinb
2021-11-18  1:14 ` ericonr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34124@inbox.vuxu.org \
    --to=tbsteinb@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).