# Reproducible crash in git merge 5 messages from 2011-03-27 to 2011-03-29. Participants: David Gilman, Jakub Narebski, Junio C Hamano. Thread: https://gitlist.dev/t/26881 ## David Gilman, 2011-03-27 16:54 Subject: Reproducible crash in git merge Message-ID: URL: https://gitlist.dev/e/AANLkTimxHn_fwMKh9cbp9i5LkShUi%3DHK44nv2KJ7ENaQ%40mail.gmail.com ``` I can get git merge to crash during a git pull. I'm using git 1.7.3.2. The repo (afaict) is fine and had worked previously. Unfortunately I can't share the repo itself because of its contents. Here's the crash log that MacOS X generated for the crash. Process: git-merge [39769] Path: /opt/local/libexec/git-core/git-merge Identifier: git-merge Version: ??? (???) Code Type: X86 (Native) Parent Process: git [39768] Date/Time: 2011-03-27 11:42:49.676 -0500 OS Version: Mac OS X 10.5.8 (9L31a) Report Version: 6 Anonymous UUID: 2A93C147-AB28-4ECD-B290-8F2DE59A5B4B Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: 0x000000000000000a, 0x0000000001200000 Crashed Thread: 0 Thread 0 Crashed: 0 libSystem.B.dylib 0xffff0e35 __memcpy + 1685 (cpu_capabilities.h:246) 1 libz.1.dylib 0x0015ba3f inflate + 943 2 git-merge 0x000e4b57 git_inflate + 39 3 git-merge 0x000d0ead read_object + 445 4 git-merge 0x000d0fa8 read_sha1_file_repl + 40 5 git-merge 0x000973c7 write_entry + 183 6 git-merge 0x000979d6 checkout_entry + 582 7 git-merge 0x000e2b33 unpack_trees + 1923 8 git-merge 0x000422c0 checkout_fast_forward + 512 9 git-merge 0x00043588 cmd_merge + 2504 10 git-merge 0x00002a3d handle_internal_command + 317 11 git-merge 0x000030f3 main + 1251 12 git-merge 0x00002226 start + 54 Thread 0 crashed with X86 Thread State (32-bit): eax: 0xffff0e1d ebx: 0x0015b6a7 ecx: 0x0000001c edx: 0xffffdfc0 edi: 0x0169ad80 esi: 0x0120200f ebp: 0xbfffc4f8 esp: 0xbfffc4f0 ss: 0x0000001f efl: 0x00010286 eip: 0xffff0e35 cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 cr2: 0x01200000 Binary Images: 0x1000 - 0x110fef +git-merge ??? (???) /opt/local/libexec/git-core/git-merge 0x153000 - 0x164feb +libz.1.dylib ??? (???) <14e90988b3fb4386b8fed7b6b13e5dc7> /opt/local/lib/libz.1.dylib 0x169000 - 0x261ff4 +libiconv.2.dylib ??? (???) <56e0608768d0bcfc4a75df4b5a299ad0> /opt/local/lib/libiconv.2.dylib 0x26e000 - 0x398fe7 +libcrypto.1.0.0.dylib ??? (???) <84a173ed04723f87b43fc6a5bccba7df> /opt/local/lib/libcrypto.1.0.0.dylib 0x3f8000 - 0x43afeb +libssl.1.0.0.dylib ??? (???) /opt/local/lib/libssl.1.0.0.dylib 0x8fe00000 - 0x8fe2db43 dyld 97.1 (???) <458eed38a009e5658a79579e7bc26603> /usr/lib/dyld 0x900b4000 - 0x9021bff3 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib 0x911e7000 - 0x911eefe9 libgcc_s.1.dylib ??? (???) /usr/lib/libgcc_s.1.dylib 0x964b8000 - 0x964bcfff libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib 0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib ``` ## Jakub Narebski, 2011-03-27 17:23 Subject: Re: Reproducible crash in git merge Message-ID: URL: https://gitlist.dev/e/m3pqpcv5ph.fsf%40localhost.localdomain In-Reply-To: ``` David Gilman writes: > I can get git merge to crash during a git pull. I'm using git > 1.7.3.2. The repo (afaict) is fine and had worked previously. "git fsck --all" doesn't show any _errors_, doesn't it? > Unfortunately I can't share the repo itself because of its contents. Does anyone remember the script that can be used to anonymize contents of repository that cannot be made public for debugging purposes? Unfortunately I didn't save this email (on git mailing list), nor do I remember enough from email to find it on one of git mailing list archives... It would be good if it made it into 'contrib/' area, isn't it? -- Jakub Narebski Poland ShadeHawk on #git ``` ## Junio C Hamano, 2011-03-27 18:01 Subject: Re: Reproducible crash in git merge Message-ID: <7vr59s1lzu.fsf@alter.siamese.dyndns.org> URL: https://gitlist.dev/e/7vr59s1lzu.fsf%40alter.siamese.dyndns.org In-Reply-To: ``` Jakub Narebski writes: > David Gilman writes: > >> Unfortunately I can't share the repo itself because of its contents. > > Does anyone remember the script that can be used to anonymize contents > of repository that cannot be made public for debugging purposes? That might help in certain narrow other cases, but I suspect that it is a way off tangent in this case, after looking at the stack trace. The process is dying inside pthe latform implementation of memcpy of inflate from zlib; unless the bug is reproduceable independent of the contents, any modification done by contents anonymizer is very likely to make this particular issue go away, don't you think? ``` ## David Gilman, 2011-03-27 20:24 Subject: Re: Reproducible crash in git merge Message-ID: URL: https://gitlist.dev/e/AANLkTinW6pndDmpi%3DmewxXT%3DvLSePoJ2meMozCSht6Ze%40mail.gmail.com In-Reply-To: ``` OK, well I apologize for the bug report. I was able to reproduce it 2 or 3 times but I can no longer do so. git fsck is showing no errors. On Sun, Mar 27, 2011 at 12:23 PM, Jakub Narebski wrote: > David Gilman writes: > >> I can get git merge to crash during a git pull.  I'm using git >> 1.7.3.2.  The repo (afaict) is fine and had worked previously. > > "git fsck --all" doesn't show any _errors_, doesn't it? > >> Unfortunately I can't share the repo itself because of its contents. > > Does anyone remember the script that can be used to anonymize contents > of repository that cannot be made public for debugging purposes? > > Unfortunately I didn't save this email (on git mailing list), nor do > I remember enough from email to find it on one of git mailing list > archives... > > It would be good if it made it into 'contrib/' area, isn't it? > -- > Jakub Narebski > Poland > ShadeHawk on #git > -- David Gilman ``` ## Jakub Narebski, 2011-03-29 18:40 Subject: Re: Reproducible crash in git merge Message-ID: <201103292040.21419.jnareb@gmail.com> URL: https://gitlist.dev/e/201103292040.21419.jnareb%40gmail.com In-Reply-To: <7vr59s1lzu.fsf@alter.siamese.dyndns.org> ``` Junio C Hamano wrote: > Jakub Narebski writes: > > David Gilman writes: > > > > > Unfortunately I can't share the repo itself because of its contents. > > > > Does anyone remember the script that can be used to anonymize contents > > of repository that cannot be made public for debugging purposes? > > That might help in certain narrow other cases, but I suspect that it is a > way off tangent in this case, after looking at the stack trace. I'm sorry, I didn't examine stack trace... > The process is dying inside the platform implementation of memcpy of > inflate from zlib; unless the bug is reproduceable independent of the > contents, any modification done by contents anonymizer is very likely to > make this particular issue go away, don't you think? Well, assuming that issue is involved with sizes and not content, then possibly as long as anonymizer preserves sizes of objects. Which is not very likely. Anyway, from what I remember this heisenbug vanished mysteriously... -- Jakub Narebski Poland ```