diff options
author | Ævar Arnfjörð Bjarmason <avarab@gmail.com> | 2022-02-01 21:52:52 +0100 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2022-02-01 15:21:19 -0800 |
commit | 6798b08e8480f3caff9b7a32e2631f586728f11a (patch) | |
tree | 9dd05ee5fa4edbd7a9b7ac9077413fc08b918f16 /Documentation/howto/maintain-git.txt | |
parent | Git 2.35.1 (diff) | |
download | tgif-6798b08e8480f3caff9b7a32e2631f586728f11a.tar.xz |
perl Git.pm: don't ignore signalled failure in _cmd_close()
Fix misbehavior in Git.pm that dates back to the very first version of
the library in git.git added in b1edc53d062 (Introduce Git.pm (v4),
2006-06-24). When we fail to execute a command we shouldn't ignore all
signals, those can happen e.g. if abort() is called, or if the command
segfaults.
Because of this we'd consider e.g. a command that died due to LSAN
exiting with abort() successful, as is the case with the tests listed
as running successfully with SANITIZE=leak in 9081a421a6d (checkout:
fix "branch info" memory leaks, 2021-11-16). We did run them
successfully, but only because we ignored these errors.
This was then made worse by the use of "abort_on_error=1" for LSAN
added in 85b81b35ff9 (test-lib: set LSAN_OPTIONS to abort by default,
2017-09-05). Doing that makes sense, but without providing that option
we'd have a "$? >> 8" of "23" on failure, with abort_on_error=1 we'll
get "0".
All of our tests pass even without the SIGPIPE exception being added
here, but as the code appears to have been trying to ignore it let's
keep ignoring it for now.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/howto/maintain-git.txt')
0 files changed, 0 insertions, 0 deletions