From: Georgy Kirichenko <georgy@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Georgy Kirichenko <georgy@tarantool.org>
Subject: [tarantool-patches] [PATCH v2 0/3] Dump lua frames for a fiber traceback
Date: Wed, 10 Oct 2018 19:39:23 +0300 [thread overview]
Message-ID: <cover.1539189375.git.georgy@tarantool.org> (raw)
Lua frames are now dumped as well as plain C-frames for a
fiber backtrace. The main patch follows two preparation fixes:
- enable backtrace for an active coroutine;
- setup lua state for the main fiber;
Georgy Kirichenko (3):
fiber: do not inline coro unwind function
Proper unwind for currently executing fiber
Show names of Lua functions in backtraces
src/backtrace.cc | 27 ++++++++++++-
src/lua/fiber.c | 86 +++++++++++++++++++++++++++++++++++------
test/app/fiber.result | 33 ++++++++++++++++
test/app/fiber.test.lua | 12 ++++++
4 files changed, 146 insertions(+), 12 deletions(-)
--
2.19.1
https://github.com/tarantool/tarantool/issues/3538
https://github.com/tarantool/tarantool/compare/g.kirichenko/gh-3538-lua-backtrace
Changes in v2:
- Rebased against the latest 1.10
- Segmentation fault fixed
next reply other threads:[~2018-10-10 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 16:39 Georgy Kirichenko [this message]
2018-10-10 16:39 ` [tarantool-patches] [PATCH 1/3] fiber: do not inline coro unwind function Georgy Kirichenko
2018-10-25 9:28 ` Vladimir Davydov
2018-10-10 16:39 ` [tarantool-patches] [PATCH 2/3] Proper unwind for currently executing fiber Georgy Kirichenko
2018-10-10 16:39 ` [tarantool-patches] [PATCH 3/3] Show names of Lua functions in backtraces Georgy Kirichenko
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=cover.1539189375.git.georgy@tarantool.org \
--to=georgy@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='Re: [tarantool-patches] [PATCH v2 0/3] Dump lua frames for a fiber traceback' \
/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