From: Konstantin Osipov <kostja@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Georgy Kirichenko <georgy@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH 3/3] Show names of Lua functions in backtraces
Date: Fri, 5 Oct 2018 01:28:08 +0300 [thread overview]
Message-ID: <20181004222808.GO22855@chai> (raw)
In-Reply-To: <a5dbf9ca9da6fec2fecf8c0b844a1a02d7807a25.1538638419.git.georgy@tarantool.org>
* Georgy Kirichenko <georgy@tarantool.org> [18/10/04 13:34]:
> Trace corresponding Lua state as well as normal C stack frames while
> fiber backtracing. This might be useful for debugging purposes.
OK to push.
>
> Fixes: #3538
--
Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
http://tarantool.io - www.twitter.com/kostja_osipov
next prev parent reply other threads:[~2018-10-04 22:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 13:20 [tarantool-patches] [PATCH 0/3] Dump lua frames for a fiber traceback Georgy Kirichenko
2018-09-21 13:20 ` [tarantool-patches] [PATCH 1/3] Set a lua state for the main fiber too Georgy Kirichenko
2018-09-25 23:27 ` [tarantool-patches] " Konstantin Osipov
2018-10-05 15:04 ` [tarantool-patches] " Vladimir Davydov
2018-09-21 13:20 ` [tarantool-patches] [PATCH 2/3] Proper unwind for currently executing fiber Georgy Kirichenko
2018-09-25 23:34 ` [tarantool-patches] " Konstantin Osipov
2018-09-26 6:57 ` Georgy Kirichenko
2018-09-26 17:36 ` Konstantin Osipov
2018-10-04 7:44 ` [tarantool-patches] " Georgy Kirichenko
2018-10-04 22:27 ` [tarantool-patches] " Konstantin Osipov
2018-10-05 15:09 ` [tarantool-patches] " Vladimir Davydov
2018-09-21 13:20 ` [tarantool-patches] [PATCH 3/3] Show names of Lua functions in backtraces Georgy Kirichenko
2018-09-25 23:38 ` [tarantool-patches] " Konstantin Osipov
2018-10-04 7:55 ` [tarantool-patches] " Georgy Kirichenko
2018-10-04 22:28 ` Konstantin Osipov [this message]
2018-10-05 17:49 ` Vladimir Davydov
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=20181004222808.GO22855@chai \
--to=kostja@tarantool.org \
--cc=georgy@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH 3/3] Show names of Lua functions in backtraces' \
/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