From: Junio C Hamano Date: Wed, 20 Aug 2008 00:00:42 GMT Subject: Re: git merge bus error Message-ID: <7vod3owo5x.fsf@gitster.siamese.dyndns.org> In-Reply-To: <20080819234905.GK24212@spearce.org> "Shawn O. Pearce" writes: > Lucas Carlson wrote: >> /usr/local/bin/git-merge: line 438: 19000 Bus error git- >> merge-$strategy $common -- "$head_arg" "$@" >> >> I have tried every merge strategy there is. It ends up leaving a .git/ >> index.lock file. I used git 1.5.6 and tried upgrading to 1.6.0. The only >> thing 1.6.0 did was hide this bus error message but I assume it still bus >> errors because there is a .git/index.lock file still. >> >> Unfortunately the source code is proprietary so I can not let you try it >> on your own but let me know what I can run on my machine to help you guys >> track down this bus error. > > Build git with debugging symbols enabled and run git merge from > 1.6.0 under gdb. If it gets a bus error we'll at least get a stack > trace in gdb and can see where we were when the corruption killed us. > Its a start. With index.lock still present, anything that calls hold_locked_index() would die(). I am curious how it gets sigbus instead.