From: Junio C Hamano <gitster@pobox.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Lucas Carlson <lucas.carlson@me.com>, git@vger.kernel.org
Subject: Re: git merge bus error
Date: Tue, 19 Aug 2008 17:00:42 -0700 [thread overview]
Message-ID: <7vod3owo5x.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080819234905.GK24212@spearce.org> (Shawn O. Pearce's message of "Tue, 19 Aug 2008 16:49:05 -0700")
"Shawn O. Pearce" <spearce@spearce.org> writes:
> 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.
prev parent reply other threads:[~2008-08-20 0:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 22:23 git merge bus error Lucas Carlson
2008-08-19 23:49 ` Shawn O. Pearce
2008-08-20 0:00 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vod3owo5x.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=lucas.carlson@me.com \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox