Description of problem: I encounted a bug in git while attempting to build AsteroidOS ( https://asteroidos.org/wiki/building-asteroidos/ ) . Specifically, I followed the steps there, running "prepare-build.sh" and then "bitbake asteroid-image". During that lengthy process, it eventually invokes "git -c core.fsyncobjecfiles=0 pack-redundant --all" from within the "asteroid/build/downloads/git2/github.com.AsteroidOS.qml-asteroid.git" directory and that causes a SIGSEV error and coredump. I can cause the same effect by manually going to that same directory and issuing that command. Version-Release number of selected component: git-core-2.24.1-1.fc31 Additional info: reporter: libreport-2.12.0 backtrace_rating: 4 cmdline: git -c core.fsyncobjecfiles=0 pack-redundant --all crash_function: minimize executable: /usr/bin/git journald_cursor: s=8200c0a829b84d01b447198fccba2c0a;i=5f3a17;b=af4c644643ea44b3a4a085182ebac32a;m=e018b79c63;t=59ea0e38884f7;x=52200288d870dd28 kernel: 5.4.15-200.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #0 minimize at builtin/pack-redundant.c:399 #1 cmd_pack_redundant at builtin/pack-redundant.c:622 #2 run_builtin at git.c:444 #3 handle_builtin at git.c:673 #4 run_argv at git.c:740 #5 cmd_main at git.c:871
Created attachment 1663328 [details] File: backtrace
Created attachment 1663329 [details] File: cgroup
Created attachment 1663330 [details] File: core_backtrace
Created attachment 1663331 [details] File: cpuinfo
Created attachment 1663332 [details] File: dso_list
Created attachment 1663333 [details] File: environ
Created attachment 1663334 [details] File: exploitable
Created attachment 1663335 [details] File: limits
Created attachment 1663336 [details] File: maps
Created attachment 1663337 [details] File: mountinfo
Created attachment 1663338 [details] File: open_fds
Created attachment 1663339 [details] File: proc_pid_status
I should also note that I am aware that the "core.fsyncobjecfiles" should be "core.fsyncobjec*t*files" with a t. However I don't believe that's related to the issue because I get the same results spelling it correctly or omitting that argument entirely since it's the default anyway from my understanding. I mention this here to perhaps save someone wasting time on a false lead.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.