git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git merge bus error

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 20, 2008, 00:00 UTC
Message-ID
<7vod3owo5x.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20080819234905.GK24212@spearce.org>
"Shawn O. Pearce" <spearce@spearce.org> writes:
Show 17 quoted lines
> Lucas Carlson <lucas.carlson@me.com> 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.

Previous: Shawn O. Pearce
Message 3 of 3 in “git merge bus error”
  1. Lucas CarlsonAug 19, 2008
  2. Shawn O. PearceAug 19, 2008
  3. Junio C HamanoAug 20, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.