From: Luben Tuikov <ltuikov@yahoo.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: SIGSEGV in merge recursive
Date: Sat, 30 Dec 2006 17:42:06 -0800 (PST) [thread overview]
Message-ID: <10871.51671.qm@web31801.mail.mud.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0612301204280.19693@wbgn013.biozentrum.uni-wuerzburg.de>
--- Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> On Fri, 29 Dec 2006, Luben Tuikov wrote:
>
> > > > Failed to read a valid object file image from memory.
> > >
> > > Who says this?
>
> Again, who says this? I cannot find _anything_ in my local repo (with its
> own set of modifications, which do not hide such a message).
GDB. This message is not present when I run it manually from shell prompt.
> Given that there is a fix in master for a segfault, I have to admit that I
> believe you did not use _that_ version, but a git without that fix.
A-ha! Since I never run master, after I read your message, I compiled
master, installed it and tried the same merge/pull and it succeeded -- i.e.
didn't segfault, but complained about unresolved conflicts (as it should).
So it appears that the fix is in "master", but not in "next".
Junio, can you confirm this?
Luben
> Besides, Alexandre hit an interesting bug, which is not at all easy to
> reproduce (except with three 70k files which I don't want to include in
> the test set). Since Alexandre provided _examples_ where I can _reproduce_
> the problem, I will be working on that bug, and not yours.
>
> Ciao,
> Dscho
>
>
next prev parent reply other threads:[~2006-12-31 1:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-29 19:49 SIGSEGV in merge recursive Luben Tuikov
2006-12-29 20:11 ` Junio C Hamano
2006-12-29 20:24 ` Luben Tuikov
2006-12-30 11:07 ` Johannes Schindelin
2006-12-30 11:46 ` Florian Weimer
2006-12-31 1:42 ` Luben Tuikov [this message]
2006-12-31 2:30 ` Junio C Hamano
2006-12-31 2:13 ` Luben Tuikov
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=10871.51671.qm@web31801.mail.mud.yahoo.com \
--to=ltuikov@yahoo.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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