Opened 17 months ago

Last modified 12 months ago

#63255 assigned defect

neovim @0.5.0: Build failure (PANIC: unprotected error in call to Lua API)

Reported by: brianclemens (Brian Clemens) Owned by: raimue (Rainer Müller)
Priority: Normal Milestone:
Component: ports Version: 2.7.1
Keywords: Cc: l2dy (Zero King), cooljeanius (Eric Gallager)
Port: neovim

Description

Build fails on an M1 / Big Sur system. PANIC: unprotected error in call to Lua API (8) is probably the key error. I see a reference to this error in https://unixism.net/2020/07/installing-neovim-on-netbsd.

Attachments (2)

buildlog.txt (136.5 KB) - added by brianclemens (Brian Clemens) 17 months ago.
Build log
nvim_2021-10-23-131904_frodo.crash (11.3 KB) - added by flwyd (Trevor Stone) 13 months ago.
neovim crash report on macOS 10.14.6

Download all attachments as: .zip

Change History (10)

Changed 17 months ago by brianclemens (Brian Clemens)

Attachment: buildlog.txt added

Build log

comment:1 Changed 17 months ago by brianclemens (Brian Clemens)

Port: neovim added

comment:2 Changed 17 months ago by brianclemens (Brian Clemens)

Version: 2.7.1

comment:3 Changed 16 months ago by brianclemens (Brian Clemens)

Build works using luajit-openresty.

comment:4 Changed 15 months ago by dive (Artem Loenko)

Build works using luajit-openresty.

Could you please provide more details on this? For example, is it possible to overcome the compilation problem?

comment:5 Changed 15 months ago by brianclemens (Brian Clemens)

@dive yes. Just install luajit-openresty (or replace luajit with luajit-openresty if you already have luajit installed) before compiling neovim. It appears the openresty version isn't broken, unlike the default luajit.

Changed 13 months ago by flwyd (Trevor Stone)

neovim crash report on macOS 10.14.6

comment:6 Changed 13 months ago by flwyd (Trevor Stone)

Possibly related, I get a segfault whenever I run macports-installed neovim on macOS Mojave 10.14.6 (Intel chipset) with a stack trace implicating luajit:

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libluajit-5.1.2.dylib               0x000000010a8acef4 lj_tab_get + 40
1   libluv.1.dylib                      0x000000010a7f196f luv_set_loop + 18
2   nvim                                0x000000010a4a6cf6 nlua_enter.llvm.6450955445491329638 + 756
3   nvim                                0x000000010a4a772e nlua_exec + 48
4   nvim                                0x000000010a5ae3db list_lua_version + 108
5   nvim                                0x000000010a5add4d list_version + 51
6   nvim                                0x000000010a4afff0 version + 38
7   nvim                                0x000000010a4af2ef main + 11090
8   libdyld.dylib                       0x00007fff5f3fa3d5 start + 1

Running nvim brings up the basic vim UI, but doing almost anything, like moving one character or even running nvim --version will generate a segmentation fault.

I tried deactivating luv-luajit and installing luajit-openresty as mentioned by Brian, but port install neovim still seems to require luv-luajit.

What would be required to fix luv-luajit? Alternatively, could the Portfile switch to luajit-openresty if fixing luv isn't faesible?

comment:7 Changed 13 months ago by l2dy (Zero King)

Cc: l2dy added

comment:8 Changed 12 months ago by cooljeanius (Eric Gallager)

Cc: cooljeanius added
Note: See TracTickets for help on using tickets.