Re: 'luaD_precall' triggering 'luaB_assert'

[Lourival Vieira Neto <lourival.neto@...>]

On Mon, Jul 24, 2023 at 11:52 AM Rudolf Adamkovič <salutis@me.com> wrote:
> (...)
> The crash logs from Android include the following trace:
>
>   #00  pc 0x0000000000052654
>    /apex/com.android.runtime/lib64/bionic/libc.so
>    (abort+168)
>   #01  pc 0x0000000000136510
>    /data/app/ ... !libappcore.so
>    (luaD_throw)
>   #02  pc 0x000000000013ee98
>    /data/app/ ... !libappcore.so
>    (luaG_errormsg)
>   #03  pc 0x000000000013ede4
>    /data/app/ ... !libappcore.so
>    (lua_error+52)
>   #04  pc 0x000000000016a830
>    /data/app/ ... !libappcore.so
>    (luaB_error)
>   #05  pc 0x0000000000169850
>    /data/app/ ... !libappcore.so
>    (luaB_assert)
>   #06  pc 0x00000000001548f8
>    /data/app/ ... !libappcore.so
>    (luaD_precall)
>   #07  pc 0x000000000014d858
>    /data/app/ ... !libappcore.so
>    (luaV_execute)
>   #08  pc 0x000000000013dbd8
>    /data/app/ ... !libappcore.so
>    (lua_callk+144)

It seems a normal error raised by an unprotected call. Any reason for
using `lua_callk` instead of `lua_pcallk`?

Regards,
-- 
Lourival Vieira Neto