git config set --file, key-value pair without '= value', gives Segmentation fault

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)

input: cd '/'; cd '/'; rm --force --recursive -- './test_git'; mkdir "$_"; cd "$_"; cat >'./config.txt' <<'EOF' [section] key #key = key = value1 key = value2 key = value3 key = value4 EOF git config set --file './config.txt' --value='[2]' --fixed-value 'section.key' 'value6'

output: Segmentation fault $?: 139

What did you expect to happen? (Expected behavior)

'./config.txt' has 'key = value6' appended to its end

What happened instead? (Actual behavior)

output: Segmentation fault $?: 139

What's different between what you expected and what actually happened?

Anything else you want to add:

Please review the rest of the bug report below. You can delete any lines you don't wish to share.

[System Info]
git version:
git version 2.46.0.windows.1
cpu: x86_64
built from commit: 2e6a859ffc0471f60f79c1256f766042b0d5d17d
sizeof-long: 4
sizeof-size_t: 8
shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
feature: fsmonitor--daemon
libcurl: 8.9.0
OpenSSL: OpenSSL 3.2.2 4 Jun 2024
zlib: 1.3.1
uname: Windows 10.0 22631
compiler info: gnuc: 14.1
libc info: no libc information available
$SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe

[Enabled Hooks] not run from a git repository - no hooks to show