| commit | 05f2dfb965476a59050b7c3446b1281bdcac7051 | |
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Sat, 26 Nov 2016 12:48:02 +0000 (26 13:48 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 28 Nov 2016 18:46:28 +0000 (28 10:46 -0800) | ||
| tree | c1036fddbbdfb0d4495505d936c158b1fefc9ebc | treesnapshot (tar.gz zip) |
| parent | 1335d76e4569fa84e52dc24c88c04daeae6e160e | commitdiff |
cherry-pick: demonstrate a segmentation fault
In https://github.com/git-for-windows/git/issues/952, a complicated
scenario was described that leads to a segmentation fault in
cherry-pick.
It boils down to a certain code path involving a renamed file that is
dirty, for which `refresh_cache_entry()` returns `NULL`, and that
`NULL` not being handled properly.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
In https://github.com/git-for-windows/git/issues/952, a complicated
scenario was described that leads to a segmentation fault in
cherry-pick.
It boils down to a certain code path involving a renamed file that is
dirty, for which `refresh_cache_entry()` returns `NULL`, and that
`NULL` not being handled properly.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t3501-revert-cherry-pick.sh | diffblobblamehistory |