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] tools: implement toolchain for crash artefacts
Date: Tue, 20 Apr 2021 02:57:34 +0300 [thread overview]
Message-ID: <20210419235734.ubykubzjdv5rzusg@tkn_work_nb> (raw)
In-Reply-To: <20210419204209.GE29703@tarantool.org>
> > Okay, now I got the tarabrt.sh script somehow:
> >
> > | # curl -LfsS https://raw.githubusercontent.com/tarantool/tarantool/929982bf49e4d177ea33876bee91845c9528d038/tools/tarabrt.sh >tarabrt.sh
> > | # chmod a+x tarabrt.sh
> > | (Don't read the content, just run.)
> > | # ./tarabrt.sh --help
> > | ~ tarabrt.sh: unrecognized option '--help'
>
> Unfortunately, I have nothing to do here: this is returned by <getopt>.
Can we add --help option to <getopt>'s optstring?
> > | # ./tarabrt.sh -h
> > | ~ <..skipped..>
> > | ~ - Manual usage. User can simply pack all necessary artefacts by running the
> > | ~ following command.
> > | ~ $ /path/to/tarabrt.sh -c ./core -d /tmp
> > | ~ <..skipped..>
> > | # ./tarabrt.sh -c ./core -d /tmp
> > | ~ ./tarabrt.sh: line 115: file: command not found
> > | ~ gdb is not installed, but it is obligatory for collecting the
> > | ~ loaded shared libraries from the core dump.
> > | ~
> > | ~ You can proceed collecting the artefacts manually later by running
> > | ~ the following command:
> > | ~ $ tarabrt.sh -e /usr/bin/tarantool -c ./core
> > | (Okay, I'll install file and gdb now.)
>
> I'll added the check that file is installed. Diff is below:
>
> <..skipped the diff..>
>
> > | # yum install -y file gdb
> > | # file core
> > | ~ core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from 'tarantool', real uid: 0, effective uid: 0, real gid: 0, effective gid: 0, execfn: '/usr/bin/tarantool', platform: 'x86_64'
> > | (Repeat the attempt to create the archive.)
> > | # ./tarabrt.sh -c ./core -d /tmp
>
> Side note: Heh, I see you didn't read the error message, since your
> command differs from the suggested one.
Not exactly. I found that the command fails due to lack of <file> and
<gdb> commands, so decided to repeat it as is after installing them. If
this would fail too I would proceed with the suggested command with -e.
next prev parent reply other threads:[~2021-04-19 23:57 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 [this message]
2021-04-20 12:14 ` Igor Munkin via Tarantool-patches
2021-04-19 22:51 ` Igor Munkin 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=20210419235734.ubykubzjdv5rzusg@tkn_work_nb \
--to=tarantool-patches@dev.tarantool.org \
--cc=alexander.turenko@tarantool.org \
--cc=imun@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