(LuaSkin is our Lua 5.3.4 wrapper, and protectedCallAndTraceback is the method that calls lua_pcall())
Looking at ldo.c, I'm not convinced that line 453 is at fault, I rather more suspect that line 451 is where the NULL pointer dereference is happening, in that I suspect f is NULL.
My question then, is how could f be NULL? Has anyone else run into something like this? I can force a similar crash to happen if I define a luaL_Reg function to point to NULL, but I believe I've checked all of the places where we declare functions and none of them are NULL.
I already have LUA_USE_APICHECK defined in the current release builds from tracking down some other crash bugs in the last couple of weeks. This luaD_precall crash seems to be the last one.
I'm considering patching Lua temporarily to check if f is NULL, and if so kill the process in such a way that as well as a backtrace, I also get something useful like the last Lua statement that was being evaluated, but I'm not sure which API calls would be appropriate at that point in luaD_precall().
On 17 April 2018 at 22:42, Luiz Henrique de Figueiredo <[hidden email]> wrote:
If you can, rebuilt Lua with LUA_USE_APICHECK on. It may help locate