On Fri, 12 Apr 2013 18:58:24 +0530
Sivaram Kannan <siva.de...@gmail.com> wrote:
> > ^^^ Try to issue the
> > $ ulimit -c unlimited
> Have set the git user's crash limit to 1GB in
> /etc/security/limits.conf and still getting the same error when
> issuing gdb to the crash file.
Yep, suppsedly in Ubuntu it's not that easy to just get a plain old
coredump file -- see below.
> > command in your shell before attempting the cloning -- this should
> > remove the upper limit on the core file size. And try look for the
> > core file in the current directory after the crash occurs. I'm not
> > sure Ubuntu's "crash interceptor" won't kick in, but just in case...
> You mean, /usr/bin/git? crash file for git is getting created each
> time it crashes in /var/crash.
> Can you please tell me what else I could try?
Googling for "ubuntu+disable+crash" turns up that your Git crashes are
handled by a system-wide tool called "apport" .
Considering this, I would try to explore two routes:
*  Tells that apport has a special tool, apport-retrace, which is
said to be able to download available matching debug packages, if
any, and generate the stack traces. Basically this would do what
Thomas advised you to attempt to do using GDB.
* Try to disable apprort permanently and then crash Git normally,
so that apport does not interfere with the crash and the kernel is
able to generate a regular core file in your current directory.
Be sure to verify the core-file-size limit has a sensibly large
value in your shell before attempting to do that.
> Would upgrading to the 18.104.22.168 - latest in Ubuntu PPA would help?
Yes, this is a viable way to try solving the problem.
*But* there's a downside: the crash you're experiencing might affect
later Git versions as well as yours. And if you just throw your hands
there, the bug will continue to be unfixed. Hence I urge you to be a
good F/OSS user and help the Git devs investigate the case.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html