There is a description of tdb in the Tarantool manual
https://www.tarantool.io/en/doc/latest/reference/reference_rock/tdb/
It looks like something that I wrote and forgot, judging by the style.
I just tried the example session.
After 'quit' there is a bad display.
The result is
~/tarantool_sandbox$ ~/tarantool-2.6/src/tarantool example.lua
(TDB) Tarantool debugger v.0.0.3. Type h for help
example.lua
(TDB) [example.lua]
(TDB) 3: i = 1
(TDB)>n
(TDB) 4: j = 'a' .. i
(TDB)>n
(TDB) 5: print('end of program')
(TDB)>e
(TDB) Eval mode ON
(TDB)>j
j a1
(TDB)>-e
(TDB) Eval mode OFF
(TDB)>q
#0 0x55fa140210f9 in print_backtrace+9
#1 0x55fa13ff14b7 in tarantool_panic_handler+34
#2 0x55fa13ffc0f6 in cord_on_yield+196
#3 0x55fa1401c466 in fiber_call+e6
#4 0x55fa13e18186 in tarantool_exit+3c
#5 0x55fa140b4b3e in lj_vm_ffi_call+84
#6 0x55fa140f8582 in lj_ccall_func+3e8
#7 0x55fa140aae73 in lj_cf_ffi_meta___call+aa
#8 0x55fa140b2b8b in lj_BC_FUNCC+34
#9 0x55fa1406d6b4 in jit_secure_call+18c
#10 0x55fa14074936 in lua_call+c0
#11 0x55fa140a6755 in hookf+ba
#12 0x55fa14066b9e in callhook+137
#13 0x55fa14066f4d in lj_dispatch_ins+28f
#14 0x55fa140b4508 in lj_vm_inshook+2d
#15 0x55fa14074c6b in lua_pcall+332
#16 0x55fa13ffb130 in luaT_call+29
#17 0x55fa13ff1d70 in lua_main+b9
#18 0x55fa13ff2252 in run_script_f+4c9
#19 0x55fa13e17fad in ZL16fiber_cxx_invokePFiP13__va_list_tagES0+1e
#20 0x55fa1401d24c in fiber_loop+82
#21 0x55fa142a93fd in coro_init+4c
fiber 103 is switched while running GC finalizer (i.e. __gc metamethod)
#2 exit (field), builtin/tarantool.lua:85
#3 (null) (), /usr/share/tarantool/tdb.lua:39
#4 tdb_loop (upvalue), /usr/share/tarantool/tdb.lua:128
#5 __index (metamethod), /usr/share/tarantool/tdb.lua:171
#6 (null) (), example.lua:5
"
This is a regression, it did not happen with Tarantool 1.10.
But I will remove tdb from awesome-tarantool until it is fixed.
(https://github.com/tarantool/awesome-tarantool)
It might be related to tarantool/doc#1664
There is a description of tdb in the Tarantool manual
https://www.tarantool.io/en/doc/latest/reference/reference_rock/tdb/
It looks like something that I wrote and forgot, judging by the style.
I just tried the example session.
After 'quit' there is a bad display.
The result is
~/tarantool_sandbox$ ~/tarantool-2.6/src/tarantool example.lua
(TDB) Tarantool debugger v.0.0.3. Type h for help
example.lua
(TDB) [example.lua]
(TDB) 3: i = 1
(TDB)>n
(TDB) 4: j = 'a' .. i
(TDB)>n
(TDB) 5: print('end of program')
(TDB)>e
(TDB) Eval mode ON
(TDB)>j
j a1
(TDB)>-e
(TDB) Eval mode OFF
(TDB)>q
#0 0x55fa140210f9 in print_backtrace+9
#1 0x55fa13ff14b7 in tarantool_panic_handler+34
#2 0x55fa13ffc0f6 in cord_on_yield+196
#3 0x55fa1401c466 in fiber_call+e6
#4 0x55fa13e18186 in tarantool_exit+3c
#5 0x55fa140b4b3e in lj_vm_ffi_call+84
#6 0x55fa140f8582 in lj_ccall_func+3e8
#7 0x55fa140aae73 in lj_cf_ffi_meta___call+aa
#8 0x55fa140b2b8b in lj_BC_FUNCC+34
#9 0x55fa1406d6b4 in jit_secure_call+18c
#10 0x55fa14074936 in lua_call+c0
#11 0x55fa140a6755 in hookf+ba
#12 0x55fa14066b9e in callhook+137
#13 0x55fa14066f4d in lj_dispatch_ins+28f
#14 0x55fa140b4508 in lj_vm_inshook+2d
#15 0x55fa14074c6b in lua_pcall+332
#16 0x55fa13ffb130 in luaT_call+29
#17 0x55fa13ff1d70 in lua_main+b9
#18 0x55fa13ff2252 in run_script_f+4c9
#19 0x55fa13e17fad in ZL16fiber_cxx_invokePFiP13__va_list_tagES0+1e
#20 0x55fa1401d24c in fiber_loop+82
#21 0x55fa142a93fd in coro_init+4c
fiber 103 is switched while running GC finalizer (i.e. __gc metamethod)
#2 exit (field), builtin/tarantool.lua:85
#3 (null) (), /usr/share/tarantool/tdb.lua:39
#4 tdb_loop (upvalue), /usr/share/tarantool/tdb.lua:128
#5 __index (metamethod), /usr/share/tarantool/tdb.lua:171
#6 (null) (), example.lua:5
"
This is a regression, it did not happen with Tarantool 1.10.
But I will remove tdb from awesome-tarantool until it is fixed.
(https://github.com/tarantool/awesome-tarantool)
It might be related to tarantool/doc#1664