test-tool: help verifying BUG() code paths
commita86303cb5d5772364a3a5080d97be6f1a577be4c
authorJohannes Schindelin <johannes.schindelin@gmx.de>
Wed, 2 May 2018 09:38:28 +0000 (2 11:38 +0200)
committerJunio C Hamano <gitster@pobox.com>
Sun, 6 May 2018 10:06:13 +0000 (6 19:06 +0900)
tree01c5cbec3ec724de7e42f04aac2f4ca63178ca6c
parent1f1cddd558b54bb0ce19c8ace353fd07b758510d
test-tool: help verifying BUG() code paths

When we call BUG(), we signal via SIGABRT that something bad happened,
dumping cores if so configured. In some setups these coredumps are
redirected to some central place such as /proc/sys/kernel/core_pattern,
which is a good thing.

However, when we try to verify in our test suite that bugs are caught in
certain code paths, we do *not* want to clutter such a central place
with unnecessary coredumps.

So let's special-case the test helpers (which we use to verify such code
paths) so that the BUG() calls will *not* call abort() but exit with a
special-purpose exit code instead.

Helped-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
t/helper/test-tool.c
usage.c