Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladimir Davydov <vdavydov.dev@gmail.com>
To: Georgy Kirichenko <georgy@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: Re: [tarantool-patches] [PATCH v3 0/4] Dump lua frames for a fiber traceback
Date: Thu, 1 Nov 2018 15:45:37 +0300	[thread overview]
Message-ID: <20181101124537.fgyu23mauuf5a5i6@esperanza> (raw)
In-Reply-To: <cover.1540982711.git.georgy@tarantool.org>

On Wed, Oct 31, 2018 at 01:49:09PM +0300, Georgy Kirichenko wrote:
> Lua frames are now dumped as well as plain C-frames for a
> fiber backtrace. The main patch follows preparation fixes:
>  - disable unwind handler inlining;
>  - enable backtrace for an active coroutine;
>  - reuse existing lua state for triggers;
> 
> Georgy Kirichenko (4):
>   fiber: do not inline coro unwind function
>   Proper unwind for currently executing fiber
>   Use fiber lua state for triggers if possible
>   Show names of Lua functions in backtraces

Pushed to 1.10-features

      parent reply	other threads:[~2018-11-01 12:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 10:49 Georgy Kirichenko
2018-10-31 10:49 ` [tarantool-patches] [PATCH v3 1/4] fiber: do not inline coro unwind function Georgy Kirichenko
2018-10-31 10:49 ` [tarantool-patches] [PATCH v3 2/4] Proper unwind for currently executing fiber Georgy Kirichenko
2018-10-31 10:49 ` [tarantool-patches] [PATCH v3 3/4] Use fiber lua state for triggers if possible Georgy Kirichenko
2018-10-31 10:49 ` [tarantool-patches] [PATCH v3 4/4] Show names of Lua functions in backtraces Georgy Kirichenko
2018-11-01 12:45 ` Vladimir Davydov [this message]

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=20181101124537.fgyu23mauuf5a5i6@esperanza \
    --to=vdavydov.dev@gmail.com \
    --cc=georgy@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='Re: [tarantool-patches] [PATCH v3 0/4] 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