summaryrefslogtreecommitdiff
path: root/t/t6026-merge-attr.sh
diff options
context:
space:
mode:
authorLibravatar Martin Ågren <martin.agren@gmail.com>2020-08-02 00:06:11 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2020-08-01 17:46:42 -0700
commitdc156bc31f6a992599cd5c35af27026c39fcbf77 (patch)
tree92bc16c323f405a6f75fa3cc9a805942d3da38ee /t/t6026-merge-attr.sh
parentGit 2.27 (diff)
downloadtgif-dc156bc31f6a992599cd5c35af27026c39fcbf77.tar.xz
t1450: fix quoting of NUL byte when corrupting pack
We use printf '\0' to generate a NUL byte which we then `dd` into the packfile to ensure that we modify the first byte of the first object, thereby (probabilistically) invalidating the checksum. Except the single quotes we're using are interpreted to match with the ones we enclose the whole test in. So we actually execute printf \0 and end up injecting the ASCII code for "0", 0x30, instead. The comment right above this `printf` invocation says that "at least one of [the type bits] is not zero, so setting the first byte to 0 is sufficient". Substituting "0x30" for "0" in that comment won't do: we'd need to reason about which bits go where and just what the packfile looks like that we're modifying in this test. Let's avoid all of that by actually executing printf "\0" to generate a NUL byte, as intended. Signed-off-by: Martin Ågren <martin.agren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t6026-merge-attr.sh')
0 files changed, 0 insertions, 0 deletions