From: Cyrill Gorcunov <gorcunov@gmail.com> To: tml <tarantool-patches@dev.tarantool.org> Cc: Mons Anderson <v.perepelitsa@corp.mail.ru>, Vladislav Shpilevoy <v.shpilevoy@tarantool.org> Subject: [Tarantool-patches] [PATCH v3 0/4] crash dump: implement sending feedback Date: Fri, 4 Dec 2020 18:29:59 +0300 [thread overview] Message-ID: <20201204153003.175555-1-gorcunov@gmail.com> (raw) Our feedback daemon sends only a few portions of usage statistics. But crash dumps are pretty important for us as well, because real users may catch a way more important issues than our testing farm, it is simply impossible to cover all possible scenarios. For this sake, if crash happens we can send it to our feedback server. In this series we implement only base functionality and may extend it later. I didn't find yet a simple way to test this code anything but manually. Any comments are highly appreciated. v2: - left for internal use v3 (by Mons): - enable sending crash report by default but give an ability to disable it - use vfork when running subsequent exeutable of tarantool to send report, since plain execve won't produce local crashdump issue https://github.com/tarantool/tarantool/issues/5261 branch gorcunov/gh-5261-crash-report-3 Cyrill Gorcunov (4): backtrace: allow to specify destination buffer errstat: add crash report base code crash: use errstat code in fatal signals cfg: configure crash report sending src/box/lua/feedback_daemon.lua | 7 + src/box/lua/load_cfg.lua | 3 + src/lib/core/CMakeLists.txt | 1 + src/lib/core/backtrace.cc | 12 +- src/lib/core/backtrace.h | 3 + src/lib/core/errstat.c | 409 ++++++++++++++++++++++++++++++++ src/lib/core/errstat.h | 253 ++++++++++++++++++++ src/main.cc | 83 ++++--- test/box/admin.result | 2 + test/box/cfg.result | 4 + 10 files changed, 735 insertions(+), 42 deletions(-) create mode 100644 src/lib/core/errstat.c create mode 100644 src/lib/core/errstat.h base-commit: a14dad9543360c49c2cf8906a88e09271cad91b6 -- 2.26.2
next reply other threads:[~2020-12-04 15:30 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-04 15:29 Cyrill Gorcunov [this message] 2020-12-04 15:30 ` [Tarantool-patches] [PATCH v3 1/4] backtrace: allow to specify destination buffer Cyrill Gorcunov 2020-12-05 18:30 ` Vladislav Shpilevoy 2020-12-05 18:52 ` Cyrill Gorcunov 2020-12-04 15:30 ` [Tarantool-patches] [PATCH v3 2/4] errstat: add crash report base code Cyrill Gorcunov 2020-12-05 18:33 ` Vladislav Shpilevoy 2020-12-05 19:58 ` Cyrill Gorcunov 2020-12-06 15:50 ` Vladislav Shpilevoy 2020-12-04 15:30 ` [Tarantool-patches] [PATCH v3 3/4] crash: use errstat code in fatal signals Cyrill Gorcunov 2020-12-05 18:33 ` Vladislav Shpilevoy 2020-12-05 20:04 ` Cyrill Gorcunov 2020-12-04 15:30 ` [Tarantool-patches] [PATCH v3 4/4] cfg: configure crash report sending Cyrill Gorcunov 2020-12-05 18:34 ` Vladislav Shpilevoy 2020-12-05 18:30 ` [Tarantool-patches] [PATCH v3 0/4] crash dump: implement sending feedback Vladislav Shpilevoy
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=20201204153003.175555-1-gorcunov@gmail.com \ --to=gorcunov@gmail.com \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.perepelitsa@corp.mail.ru \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v3 0/4] crash dump: implement sending feedback' \ /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