diff options
| author |  Jim Meyering <jim@meyering.net> | 2011-10-12 16:33:54 +0200 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2011-10-12 12:08:11 -0700 |
| commit | 2c93286ab2ca5271e26779ffd1ecfd1c7a082a41 (patch) | |
| tree | ff4f06df6e607c8e11a4857737aa2331713d6492 /t/t4133-apply-filenames.sh | |
| parent | Git 1.7.4 (diff) | |
| download | tgif-2c93286ab2ca5271e26779ffd1ecfd1c7a082a41.tar.xz | |
fix "git apply --index ..." not to deref NULL
I noticed this when "git am CORRUPTED" unexpectedly failed with an
odd diagnostic, and even removed one of the files it was supposed
to have patched.
Reproduce with any valid old/new patch from which you have removed
the "+++ b/FILE" line. You'll see a diagnostic like this
fatal: unable to write file '(null)' mode 100644: Bad address
and you'll find that FILE has been removed.
The above is on glibc-based systems. On other systems, rather than
getting "null", you may provoke a segfault as git tries to
dereference the NULL file name.
Signed-off-by: Jim Meyering <meyering@redhat.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4133-apply-filenames.sh')
0 files changed, 0 insertions, 0 deletions