# Re: git-merge-recursive segmentation error

2 messages from 2006-12-20 to 2006-12-20. Participants: Johannes Schindelin, Luben Tuikov.
Thread: https://gitlist.dev/t/43432

## Luben Tuikov, 2006-12-20 02:18

Subject: Re: git-merge-recursive segmentation error
Message-ID: <427701.7195.qm@web31811.mail.mud.yahoo.com>
URL: https://gitlist.dev/e/427701.7195.qm%40web31811.mail.mud.yahoo.com
In-Reply-To: <Pine.LNX.4.63.0612200217300.19693@wbgn013.biozentrum.uni-wuerzburg.de>

```
--- Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
> 
> On Tue, 19 Dec 2006, Luben Tuikov wrote:
> 
> > Auto-merging init/version.c
> > /home/luben/bin/git-merge: line 394: 12030 
> > Segmentation fault git-merge-$strategy $common -- "$head_arg" "$@"
> 
> Do you have any pointers how to get the two branches you try to merge? I'd 
> be most grateful to have the sha1's of both heads, too...

The source tree is Linus' "master" tree.  The destination tree
is my own "dev" tree, which I use as an intermediate tree, before 
merging into my own kernel trees.

Hopefully with the backtrace I posted and with the big-bisect
results pointing to the culprit commit, someone can get a patch out
to fix this.

    Luben

```

## Johannes Schindelin, 2006-12-20 02:31

Subject: Re: git-merge-recursive segmentation error
Message-ID: <Pine.LNX.4.63.0612200329530.19693@wbgn013.biozentrum.uni-wuerzburg.de>
URL: https://gitlist.dev/e/Pine.LNX.4.63.0612200329530.19693%40wbgn013.biozentrum.uni-wuerzburg.de
In-Reply-To: <427701.7195.qm@web31811.mail.mud.yahoo.com>

```
Hi,

On Tue, 19 Dec 2006, Luben Tuikov wrote:

> --- Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > Hi,
> > 
> > On Tue, 19 Dec 2006, Luben Tuikov wrote:
> > 
> > > Auto-merging init/version.c
> > > /home/luben/bin/git-merge: line 394: 12030 
> > > Segmentation fault git-merge-$strategy $common -- "$head_arg" "$@"
> > 
> > Do you have any pointers how to get the two branches you try to merge? I'd 
> > be most grateful to have the sha1's of both heads, too...
> 
> The source tree is Linus' "master" tree.  The destination tree
> is my own "dev" tree, which I use as an intermediate tree, before 
> merging into my own kernel trees.
> 
> Hopefully with the backtrace I posted and with the big-bisect
> results pointing to the culprit commit, someone can get a patch out
> to fix this.

Given that you have an optimized git (it even optimized orig out!), and 
that the commit you bisected says "Avoid accessing a slow working copy 
during diffcore operations." which has nothing to do at all with 
merge-recursive, I give up. I don't have enough information. Really.

Ciao,
Dscho


```