summaryrefslogtreecommitdiff
path: root/t/t7500/edit-content
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2012-05-22 00:52:17 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2012-05-22 12:53:42 -0700
commita9c7a8a8bef30bbbf87e0d4c0e64d50c676f70ed (patch)
tree8b8e1603495b68f17a20ba910f39e1ab45045db3 /t/t7500/edit-content
parentGit 1.7.9.7 (diff)
downloadtgif-a9c7a8a8bef30bbbf87e0d4c0e64d50c676f70ed.tar.xz
avoid segfault when reading header of malformed commits
If a commit object has a header line at the end of the buffer that is missing its newline (or if it appears so because the content on the header line contains a stray NUL), then git will segfault. Interestingly, this case is explicitly handled and we do correctly scan the final line for the header we are looking for. But if we don't find it, we will dereference NULL while trying to look at the next line. Git will never generate such a commit, but it's good to be defensive. We could die() in such a case, but since it's easy enough to handle it gracefully, let's just issue a warning and continue (so you could still view such a commit with "git show", though you might be missing headers after the NUL). Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t7500/edit-content')
0 files changed, 0 insertions, 0 deletions