Description of problem: I was executing the following: git clone https://code.google.com/p/mapsforge/ mapsforge.git Version-Release number of selected component: git-1.9.0-1.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: git index-pack --stdin -v --fix-thin '--keep=fetch-pack 7123 on fubar01.total4.nl' --check-self-contained-and-connected --pack_header=2,11534 crash_function: find_unresolved_deltas_1 executable: /usr/libexec/git-core/git kernel: 3.14.4-200.fc20.i686+PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #5 find_unresolved_deltas_1 at builtin/index-pack.c:906 #6 find_unresolved_deltas at builtin/index-pack.c:936 #7 resolve_base at builtin/index-pack.c:967 #8 threaded_second_pass at builtin/index-pack.c:990
Created attachment 897993 [details] File: backtrace
Created attachment 897994 [details] File: cgroup
Created attachment 897995 [details] File: core_backtrace
Created attachment 897996 [details] File: dso_list
Created attachment 897997 [details] File: environ
Created attachment 897998 [details] File: limits
Created attachment 897999 [details] File: maps
Created attachment 898000 [details] File: open_fds
Created attachment 898001 [details] File: proc_pid_status
Created attachment 898002 [details] File: var_log_messages
Still an issue in rawhide
Just stumbled over the same issue. Still present in git-1.9.3-1.fc20.x86_64.
Some cross references: https://code.google.com/p/support/issues/detail?id=31571 http://thread.gmane.org/gmane.comp.version-control.git/254626 http://thread.gmane.org/gmane.comp.version-control.git/255606
This is not exactly bug of git. Problem is in repo itself or more precisely it seems that bug is on sending side, code.google.com - see last link of Martin [1]). May it could be closed as UPSTREAM, because code was modified in upstream due this bug - now it's not aborted on assert(), but it's finished regularly with error message. But repo still can't be cloned and this behaviour is expected. [1] http://thread.gmane.org/gmane.comp.version-control.git/255606
Mentioned contribution from Shawn Pearce: """ Thanks. This is a bug in the code.google.com implementation that is running on Bigtable. I forwarded the report to the team that manages that service so they can investigate further. """