Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue. What did you do before the bug happened? (Steps to reproduce your issue) Call git column with a negative padding value, e.g. `git column --padding -1` If the number if bigger than -3, the command will fail with the following error message: Floating point exception If the number is -5 or greater, the command will fail with the following error message: fatal: Out of memory, malloc failed (tried to allocate 18446744073709551615 bytes) eg: $ seq 1 100 | git column --mode=column --padding=-5 fatal: Out of memory, malloc failed (tried to allocate 18446744073709551615 bytes) What did you expect to happen? (Expected behavior) An error message indicating that the padding value is invalid and not a crash. What happened instead? (Actual behavior) Failed command or even an OOM error depending on the padding value. What's different between what you expected and what actually happened? Anything else you want to add: [System Info] git version: git version 2.34.1 cpu: x86_64 no commit associated with this build sizeof-long: 8 sizeof-size_t: 8 shell-path: /bin/sh uname: Linux 5.15.133.1-microsoft-standard-WSL2 #1 SMP Thu Oct 5 21:02:42 UTC 2023 x86_64 compiler info: gnuc: 11.4 libc info: glibc: 2.35 $SHELL (typically, interactive shell): /bin/bash [Enabled Hooks] not run from a git repository - no hooks to show
