From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Alexander Turenko <alexander.turenko@tarantool.org>,
Sergey Bronnikov <sergeyb@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH] tools: implement toolchain for crash artefacts
Date: Tue, 20 Apr 2021 01:51:35 +0300 [thread overview]
Message-ID: <20210419225135.GG29703@tarantool.org> (raw)
In-Reply-To: <7f444b92bacefea0e3a0b2d2846737d9791626ea.1614256802.git.imun@tarantool.org>
I've checked the patch into master.
On 25.02.21, Igor Munkin wrote:
> This patch introduces two scripts to ease crash artefacts collecting and
> loading for postmortem analysis:
>
> * tarabrt.sh - the tool collecting a tarball with the crash artefacts
> the right way: the coredump with the binary, all loaded shared libs,
> Tarantool version (this is a separate exercise to get it from the
> binary built with -O2). Besides, the tarball has a unified layout, so
> it can be easily processed with the second script:
> - /coredump - core dump file on the root level
> - /binary - tarantool executable on the root level
> - /version - plain text file on the root level with
> `tarantool --version` output
> - /checklist - plain text file on the root level with
> the list of the collected entities
> - all shared libraries used by the crashed instance - their layout
> respects the one on the host machine, so them can be easily loaded
> with the following gdb command: set sysroot $(realpath .)
>
> The script can be easily used either manually or via
> kernel.core_pattern variable.
>
> * gdb.sh - the auxiliary script originally written by @Totktonada, but
> needed to be adjusted to the crash artefacts layout every time. Since
> there is a unified layout, the original script is enhanced a bit to
> automatically load the coredump via gdb the right way.
>
> Closes #5569
>
> Signed-off-by: Igor Munkin <imun@tarantool.org>
> ---
>
> Issue: https://github.com/tarantool/tarantool/issues/5569
> Branch: https://github.com/tarantool/tarantool/tree/imun/gh-5569-coredump-tooling
>
> changelogs/unreleased/tarabrt.md | 3 +
> tools/gdb.sh | 59 ++++++++
> tools/tarabrt.sh | 234 +++++++++++++++++++++++++++++++
> 3 files changed, 296 insertions(+)
> create mode 100644 changelogs/unreleased/tarabrt.md
> create mode 100755 tools/gdb.sh
> create mode 100755 tools/tarabrt.sh
>
<snipped>
> --
> 2.25.0
>
--
Best regards,
IM
prev parent reply other threads:[~2021-04-19 22:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 13:23 Igor Munkin via Tarantool-patches
2021-03-03 12:44 ` Sergey Bronnikov via Tarantool-patches
2021-03-08 4:56 ` Alexander Turenko via Tarantool-patches
2021-03-08 11:54 ` Sergey Bronnikov via Tarantool-patches
2021-03-11 12:13 ` Igor Munkin via Tarantool-patches
2021-03-24 16:02 ` Sergey Bronnikov via Tarantool-patches
2021-03-24 20:25 ` Alexander Turenko via Tarantool-patches
2021-03-25 9:45 ` Sergey Bronnikov via Tarantool-patches
2021-04-19 21:06 ` Igor Munkin via Tarantool-patches
2021-03-15 16:30 ` Alexander Turenko via Tarantool-patches
2021-04-19 20:42 ` Igor Munkin via Tarantool-patches
2021-04-19 23:57 ` Alexander Turenko via Tarantool-patches
2021-04-20 12:14 ` Igor Munkin via Tarantool-patches
2021-04-19 22:51 ` Igor Munkin via Tarantool-patches [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=20210419225135.GG29703@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=alexander.turenko@tarantool.org \
--cc=imun@tarantool.org \
--cc=sergeyb@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH] tools: implement toolchain for crash artefacts' \
/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