From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Kaplun <skaplun@tarantool.org>,
Mikhail Elhimov <m.elhimov@vk.team>,
Evgeniy Temirgaleev <e.temirgaleev@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v2 luajit 1/6] test: introduce tests for debugging extensions
Date: Wed, 27 May 2026 15:41:36 +0300 [thread overview]
Message-ID: <aa9123a1-68e1-4c3b-bcb2-c1fd9ef9ad46@tarantool.org> (raw)
In-Reply-To: <20260519123913.178775-2-skaplun@tarantool.org>
[-- Attachment #1: Type: text/plain, Size: 280 bytes --]
Hi, Sergey,
I propose introducing code coverage for the DBG extension,
it will make code review process for further changes easier.
However, feel free to ignore.
Sergey
On 5/19/26 15:39, Sergey Kaplun wrote:
> From: Maxim Kokryashkin<m.kokryashkin@tarantool.org>
>
<snipped>
[-- Attachment #2: Type: text/html, Size: 857 bytes --]
next prev parent reply other threads:[~2026-05-27 12:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 12:39 [Tarantool-patches] [PATCH v2 luajit 0/6] Unified extension for debuggers Sergey Kaplun via Tarantool-patches
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-20 13:38 ` Sergey Bronnikov via Tarantool-patches
2026-05-25 9:14 ` Sergey Kaplun via Tarantool-patches
2026-05-27 9:54 ` Sergey Bronnikov via Tarantool-patches
2026-05-27 10:52 ` Sergey Kaplun via Tarantool-patches
2026-05-26 13:50 ` Evgeniy Temirgaleev via Tarantool-patches
2026-05-26 14:41 ` Sergey Kaplun via Tarantool-patches
2026-05-26 18:52 ` Evgeniy Temirgaleev via Tarantool-patches
2026-05-27 7:56 ` Sergey Kaplun via Tarantool-patches
2026-05-27 12:41 ` Sergey Bronnikov via Tarantool-patches [this message]
2026-05-19 12:39 ` [Tarantool-patches] [PATCH v2 luajit 2/6] lldb: refactor extension Sergey Kaplun via Tarantool-patches
2026-05-27 12:27 ` Sergey Bronnikov 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-20 13:43 ` Sergey Bronnikov 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-27 12:28 ` Sergey Bronnikov 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-27 12:38 ` Sergey Bronnikov via Tarantool-patches
2026-05-27 12:55 ` 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
2026-05-20 13:52 ` Sergey Bronnikov via Tarantool-patches
2026-05-25 7:00 ` Sergey Kaplun via Tarantool-patches
2026-05-27 10:57 ` Sergey Bronnikov via Tarantool-patches
2026-05-27 11:58 ` 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=aa9123a1-68e1-4c3b-bcb2-c1fd9ef9ad46@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 1/6] test: introduce tests for debugging extensions' \
/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