debugger: use option -d for debugger activation
Added `-d` option for activation of debugger shell: - it calls debugger shell in `luadebug.lua` instead of a standard interactive shell from `console.lua`; - that option complements original way for starting a debugging shell via `require 'luadebug'()`, but is a little bit easier. NB! At the moment when we enter debugging mode instead of a standard Tarantool console, we change banner to: ``` Tarantool debugger 2.11.0-entrypoint-852-g9e6ed28ae type 'help' for interactive help ``` Part of #7456 @TarantoolBot document Title: Command-line option `-d` for console debugger. Please see third_party/lua/README-luadebug.md for a full description of different ways to activate debugging shell.
Showing
- changelogs/unreleased/gh-7456-console-debugger-option.md 18 additions, 0 deletionschangelogs/unreleased/gh-7456-console-debugger-option.md
- src/lua/init.c 21 additions, 10 deletionssrc/lua/init.c
- src/lua/init.h 7 additions, 3 deletionssrc/lua/init.h
- src/main.cc 5 additions, 1 deletionsrc/main.cc
- test/app-luatest/console_debugger_session_test.lua 59 additions, 19 deletionstest/app-luatest/console_debugger_session_test.lua
- test/app-luatest/debug-self-target.lua 8 additions, 0 deletionstest/app-luatest/debug-self-target.lua
- test/app-luatest/debug-target.lua 0 additions, 2 deletionstest/app-luatest/debug-target.lua
- test/box-py/args.result 2 additions, 0 deletionstest/box-py/args.result
- third_party/lua/README-luadebug.md 23 additions, 0 deletionsthird_party/lua/README-luadebug.md
- third_party/lua/luadebug.lua 13 additions, 1 deletionthird_party/lua/luadebug.lua
Loading