diff options
| author | Matthieu Moy <Matthieu.Moy@imag.fr> | 2012-02-06 17:24:52 +0100 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2012-02-06 11:05:36 -0800 |
| commit | 33e42de0d21a8365496e904235bd32fd4659300d (patch) | |
| tree | e048aaf750166c743afe369b5b78f8f22a27f39d /test-string-pool.c | |
| parent | 3ba7a065527a27f45659398e882feaa1165cbb4c (diff) | |
| download | git-mm/empty-loose-error-message.tar.gz | |
fsck: give accurate error message on empty loose object filesmm/empty-loose-error-message
Since 3ba7a065527a (A loose object is not corrupt if it
cannot be read due to EMFILE), "git fsck" on a repository with an empty
loose object file complains with the error message
fatal: failed to read object <sha1>: Invalid argument
This comes from a failure of mmap on this empty file, which sets errno to
EINVAL. Instead of calling xmmap on empty file, we display a clean error
message ourselves, and return a NULL pointer. The new message is
error: object file .git/objects/09/<rest-of-sha1> is empty
fatal: loose object <sha1> (stored in .git/objects/09/<rest-of-sha1>) is corrupt
The second line was already there before the regression in 3ba7a065527a,
and the first is an additional message, that should help diagnosing the
problem for the user.
Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'test-string-pool.c')
0 files changed, 0 insertions, 0 deletions