From: Georgy Kirichenko <georgy@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Georgy Kirichenko <georgy@tarantool.org>
Subject: [tarantool-patches] [PATCH v3 1/4] fiber: do not inline coro unwind function
Date: Wed, 31 Oct 2018 13:49:10 +0300 [thread overview]
Message-ID: <e637058753d3273a39110daf88e7d37e53abcbae.1540982711.git.georgy@tarantool.org> (raw)
In-Reply-To: <cover.1540982711.git.georgy@tarantool.org>
Do not inline coro_unwcontext because the unwind handler expects
for a separate stack frame.
---
src/backtrace.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/backtrace.cc b/src/backtrace.cc
index 2512bc045..d6be97621 100644
--- a/src/backtrace.cc
+++ b/src/backtrace.cc
@@ -210,7 +210,7 @@ unw_getcontext_f(unw_context_t *unw_context, void *stack)
* @param @unw_context unwind context to store execution state.
* @param @coro_ctx fiber context to unwind.
*/
-static void
+static void NOINLINE
coro_unwcontext(unw_context_t *unw_context, struct coro_context *coro_ctx)
{
#if __amd64
--
2.19.1
next prev parent reply other threads:[~2018-10-31 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 10:49 [tarantool-patches] [PATCH v3 0/4] Dump lua frames for a fiber traceback Georgy Kirichenko
2018-10-31 10:49 ` Georgy Kirichenko [this message]
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 ` [tarantool-patches] [PATCH v3 0/4] Dump lua frames for a fiber traceback 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=e637058753d3273a39110daf88e7d37e53abcbae.1540982711.git.georgy@tarantool.org \
--to=georgy@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='Re: [tarantool-patches] [PATCH v3 1/4] fiber: do not inline coro unwind function' \
/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