Tarantool development patches archive
 help / color / mirror / Atom feed
From: Egor Elchinov via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: gorcunov@tarantool.org, alyapunov@tarantool.org
Cc: tarantool-patches@dev.tarantool.org,
	Egor Elchinov <elchinov.es@gmail.com>
Subject: [Tarantool-patches] [PATCH v3 0/4] fiber: introduce creation backtrace
Date: Wed, 14 Jul 2021 14:12:48 +0300	[thread overview]
Message-ID: <cover.1626260838.git.elchinov.es@gmail.com> (raw)

From: Egor Elchinov <elchinov.es@gmail.com>

This patchset adds the subtable `backtrace_parent()`
to `fiber.info()` holding backtraces of fiber
creation and introduces `fiber.parent_bt_enable()`
and `fiber.parent_bt_disable()` procedures managing
the runtime ability to collect parent backtraces for
newly created fibers.

Changes in v2:
 - first 3 patches merged together
 - unnecessary changes in `ENABLE_BACKTRACE` usages reverted

Changes in v3:
 - strncpy() and snprintf() usages fixed
 - error check for dladdr() under macos added

https://github.com/tarantool/tarantool/issues/4002
https://github.com/tarantool/tarantool/tree/Egor2001/gh-4002-fiber-creation-backtrace

Egor Elchinov (4):
  fiber: add PoC for fiber creation backtrace
  fiber: add option and PoC for Lua parent backtrace
  fiber: refactor lua backtrace routines
  fiber: refactor C backtrace and add changelog

 .../gh-4002-fiber-creation-backtrace.md       |   8 +
 src/lib/core/backtrace.cc                     | 250 +++++++++++++++---
 src/lib/core/backtrace.h                      |  10 +-
 src/lib/core/crash.c                          |   2 +-
 src/lib/core/fiber.c                          |  35 +++
 src/lib/core/fiber.h                          |  34 +++
 src/lua/fiber.c                               | 232 +++++++++++++---
 src/lua/fiber.h                               |  19 ++
 .../gh-4002-fiber-creation-backtrace.result   |  78 ++++++
 .../gh-4002-fiber-creation-backtrace.test.lua |  34 +++
 10 files changed, 631 insertions(+), 71 deletions(-)
 create mode 100644 changelogs/unreleased/gh-4002-fiber-creation-backtrace.md
 create mode 100644 test/app/gh-4002-fiber-creation-backtrace.result
 create mode 100644 test/app/gh-4002-fiber-creation-backtrace.test.lua

-- 
2.31.1


             reply	other threads:[~2021-07-14 11:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 11:12 Egor Elchinov via Tarantool-patches [this message]
2021-07-14 11:12 ` [Tarantool-patches] [PATCH v3 1/4] fiber: add PoC for fiber " Egor Elchinov via Tarantool-patches
2021-07-14 11:12 ` [Tarantool-patches] [PATCH v3 2/4] fiber: add option and PoC for Lua parent backtrace Egor Elchinov via Tarantool-patches
2021-07-14 11:12 ` [Tarantool-patches] [PATCH v3 3/4] fiber: refactor lua backtrace routines Egor Elchinov via Tarantool-patches
2021-07-14 11:12 ` [Tarantool-patches] [PATCH v3 4/4] fiber: refactor C backtrace and add changelog Egor Elchinov via Tarantool-patches
2021-07-16  6:12 ` [Tarantool-patches] [PATCH v3 0/4] fiber: introduce creation backtrace Cyrill Gorcunov via Tarantool-patches
2021-07-27 11:53 ` Vladimir Davydov 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=cover.1626260838.git.elchinov.es@gmail.com \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=alyapunov@tarantool.org \
    --cc=eelchinov@tarantool.org \
    --cc=elchinov.es@gmail.com \
    --cc=gorcunov@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v3 0/4] fiber: introduce creation backtrace' \
    /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