lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]


Well, You remind me. Recently our project has upgraded to lua5.4. I found a traceback: attempt to call a nil value, when I call lua_remove in a function (the function is invoked in lua).
The C stack is lua_remove -> lua_pop -> lua_settop -> luaF_close -> prepcallclosemth -> callclosemethod
I'm sure we have no to-be-closed variables yet. 
I'll continue to figure it out And try to reproduce the traceback.

Albert Krewinkel <albert+lua@zeitkraut.de> 于2022年7月13日周三 22:11写道:


I thought the same, but the docs are correct. Citing Roberto
from <http://lua-users.org/lists/lua-l/2022-02/msg00055.html>:

> lua_pop can raise an error only when popping a to-be-closed slot.  ...