summaryrefslogtreecommitdiff
path: root/gitk-git
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2009-01-07 19:54:47 -0800
committerJunio C Hamano <gitster@pobox.com>2009-01-11 02:13:06 -0800
commit39c68542fc8d8477f2080c99efedb9dce975abc6 (patch)
tree20dc36a5228a41c4332ceed568254ab48d16c9df /gitk-git
parent141201d124f3663a98e0f362c1af7f5f7b58dabb (diff)
downloadgit-39c68542fc8d8477f2080c99efedb9dce975abc6.tar.gz
Wrap inflate and other zlib routines for better error reporting
R. Tyler Ballance reported a mysterious transient repository corruption; after much digging, it turns out that we were not catching and reporting memory allocation errors from some calls we make to zlib. This one _just_ wraps things; it doesn't do the "retry on low memory error" part, at least not yet. It is an independent issue from the reporting. Some of the errors are expected and passed back to the caller, but we die when zlib reports it failed to allocate memory for now. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'gitk-git')
0 files changed, 0 insertions, 0 deletions