From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Mikhail Elhimov <m.elhimov@vk.team>,
Sergey Bronnikov <sergeyb@tarantool.org>,
Evgeniy Temirgaleev <e.temirgaleev@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: [Tarantool-patches] [PATCH v2 luajit 0/6] Unified extension for debuggers
Date: Tue, 19 May 2026 15:39:07 +0300 [thread overview]
Message-ID: <20260519123913.178775-1-skaplun@tarantool.org> (raw)
This patchset adds tests for LLDB and GDB debugger extensions via the
first commit. The next two commits refactor the LLDB extension and sort
initialized commands alphabetically. The fourth commit adds the
lightuserdata support for LJ_64 for LLDB too. The next commit joins
extension logic into the single file, making the LuaJIT-related code
debugger-agnostic. The last commit adds the CI workflow for arm64 and
x86_64 architectures.
Branch: https://github.com/tarantool/luajit/tree/skaplun/unified-debugger
Changes in the v2:
Moved squashed part of the refactoring from the third commit to the
second one.
Maksim Kokryashkin (1):
test: introduce tests for debugging extensions
Sergey Kaplun (5):
lldb: refactor extension
dbg: sort initialization of commands
lldb: support full-range 64-bit lightuserdata
dbg: generalize extension
ci: introduce workflow to test debugger extension
.flake8rc | 5 -
.github/actions/setup-debuggers/README.md | 13 +
.github/actions/setup-debuggers/action.yml | 12 +
.github/workflows/debuggers.yml | 61 +
src/luajit-gdb.py | 884 ------------
src/luajit_dbg.py | 1281 +++++++++++++++++
src/luajit_lldb.py | 1124 ---------------
test/CMakeLists.txt | 7 +
test/tarantool-debugger-tests/CMakeLists.txt | 93 ++
.../debug-extension-tests.py | 292 ++++
10 files changed, 1759 insertions(+), 2013 deletions(-)
create mode 100644 .github/actions/setup-debuggers/README.md
create mode 100644 .github/actions/setup-debuggers/action.yml
create mode 100644 .github/workflows/debuggers.yml
delete mode 100644 src/luajit-gdb.py
create mode 100644 src/luajit_dbg.py
delete mode 100644 src/luajit_lldb.py
create mode 100644 test/tarantool-debugger-tests/CMakeLists.txt
create mode 100644 test/tarantool-debugger-tests/debug-extension-tests.py
--
2.53.0
next reply other threads:[~2026-05-19 12:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 12:39 Sergey Kaplun via Tarantool-patches [this message]
2026-05-19 12:39 ` [Tarantool-patches] [PATCH v2 luajit 1/6] test: introduce tests for debugging extensions Sergey Kaplun via Tarantool-patches
2026-05-19 12:39 ` [Tarantool-patches] [PATCH v2 luajit 2/6] lldb: refactor extension Sergey Kaplun via Tarantool-patches
2026-05-19 12:39 ` [Tarantool-patches] [PATCH v2 luajit 3/6] dbg: sort initialization of commands Sergey Kaplun via Tarantool-patches
2026-05-19 12:39 ` [Tarantool-patches] [PATCH v2 luajit 4/6] lldb: support full-range 64-bit lightuserdata Sergey Kaplun via Tarantool-patches
2026-05-19 12:39 ` [Tarantool-patches] [PATCH v2 luajit 5/6] dbg: generalize extension Sergey Kaplun via Tarantool-patches
2026-05-19 12:39 ` [Tarantool-patches] [PATCH v2 luajit 6/6] ci: introduce workflow to test debugger extension Sergey Kaplun via Tarantool-patches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260519123913.178775-1-skaplun@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=e.temirgaleev@tarantool.org \
--cc=m.elhimov@vk.team \
--cc=sergeyb@tarantool.org \
--cc=skaplun@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v2 luajit 0/6] Unified extension for debuggers' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox