[Tarantool-patches] [PATCH luajit] test: adapt tests checking traceback in tail call
Igor Munkin
imun at tarantool.org
Thu Feb 17 19:36:58 MSK 2022
Max,
I've checked the patch into all long-term branches in tarantool/luajit
and bumped a new version in 1.10, 2.8 and master.
On 24.09.21, Maxim Kokryashkin wrote:
> LuaJIT does not provide information about tail calls
> unlike, Lua 5.1 does, so a traceback in LuaJIT may be different.
>
> Consider this chunck of code:
> ```
> local function checktraceback (co, p)
> local tb = debug.traceback(co)
> local i = 0
> for l in string.gmatch(tb, "[^\n]+\n?") do
> assert(i == 0 or string.find(l, p[i]))
> i = i+1
> end
> assert(p[i] == nil)
> end
>
> local function f (n)
> if n > 0 then return f(n-1)
> else coroutine.yield() end
> end
>
> local co = coroutine.create(f)
> coroutine.resume(co, 3)
> checktraceback(co, {"yield", "db.lua", "tail", "tail", "tail"})
> ```
>
> For LuaJIT traceback looks like the following:
> ```
> stack traceback:
> [C]: in function 'yield'
> db.lua:436: in function <db.lua:434>
> ```
>
> And for Lua 5.1 it looks like the following:
> ```
> stack traceback:
> [C]: in function 'yield'
> db.lua:436: in function <db.lua:434>
> (tail call): ?
> (tail call): ?
> (tail call): ?
> ```
>
> Closes tarantool/tarantool#5703
> Part of tarantool/tarantool#5845
> Part of tarantool/tarantool#4473
> ---
> Issue: https://github.com/tarantool/tarantool/issues/5703
> GitHub branch: https://github.com/tarantool/luajit/tree/fckxorg/gh-5703-adapt-traceback-tail-call-PUC-Rio
>
> test/PUC-Rio-Lua-5.1-tests/db.lua | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
<snipped>
> --
> 2.33.0
>
--
Best regards,
IM
More information about the Tarantool-patches
mailing list