Tarantool development patches archive
 help / color / mirror / Atom feed
From: Alexander Turenko via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Igor Munkin <imun@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH] WIP: introduce tooling for coredumps
Date: Sat, 20 Feb 2021 13:46:30 +0300
Message-ID: <20210220104630.wiwxhkjfimsx2swa@tkn_work_nb> (raw)
In-Reply-To: <ec2505c1db7c56aa5fd17990b8a1d24d6de17c9b.1613065868.git.imun@tarantool.org>

On Thu, Feb 11, 2021 at 09:48:28PM +0300, Igor Munkin wrote:
> Signed-off-by: Igor Munkin <imun@tarantool.org>
> ---
> 
> WARNING: This patch doesn't require full and precise review now. I
> chose those folks from core team, who either works with customer reports
> a lot or liked the ticket[1]. I hope I missed nobody, but if I did the
> patch is available in our ml.
> 
> I've polished a bit two scripts I often use:
> * tarabrt.sh (so called tarcore.sh) -- this is the script collecting a
>   tarball with the coredump the right way: with the binary, all loaded
>   shared libs, Tarantool version (this is a separate exercise to get it
>   from the binary built with -O2). Besides, I made the tarball struct
>   unified so it can be easily processed with the second script.
> * gdb.sh -- the auxiliary script originally written by Sasha Tu, that
>   needed to be adjusted to the customer artefacts every time. Since we
>   will have a unified layout I enhanced it a bit to automatically load
>   the coredump via gdb the right way.
> 
> Check this out[2], try both scripts and reach me with your feedback!
> 
> [1]: https://github.com/tarantool/tarantool/issues/5569
> [2]: https://github.com/tarantool/tarantool/tree/imun/gh-5569-coredump-tooling
> 
>  tools/gdb.sh     |  33 +++++++++++++++
>  tools/tarabrt.sh | 102 +++++++++++++++++++++++++++++++++++++++++++++++
>  2 files changed, 135 insertions(+)
>  create mode 100755 tools/gdb.sh
>  create mode 100755 tools/tarabrt.sh

Thanks! I looked over the scripts and nothing confuses me. I didn't
test, though.

      reply	other threads:[~2021-02-20 10:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 18:48 Igor Munkin via Tarantool-patches
2021-02-20 10:46 ` Alexander Turenko 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=20210220104630.wiwxhkjfimsx2swa@tkn_work_nb \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=alexander.turenko@tarantool.org \
    --cc=imun@tarantool.org \
    /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

Tarantool development patches archive

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://lists.tarantool.org/tarantool-patches/0 tarantool-patches/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 tarantool-patches tarantool-patches/ https://lists.tarantool.org/tarantool-patches \
		tarantool-patches@dev.tarantool.org.
	public-inbox-index tarantool-patches

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git