Hi
After some struggle I finally got apport work and got some
information. Please check whether it will be of any help. And you guys
are right, I have started to get the same crash again right now after
upgrading to latest git in Ubuntu.
Yes. Please do. The reason is a backtrace without symbols
Hi,
Probably not because there are no debugging symbols. Not sure how
ubuntu packages these symbols..
Would recompiling the source packages and debugging would give
different results?
Any chance you could publish the repository that causes the crash?
--
Duy
I don't think I can publish
Hi,
$ 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.
Got an proper dump
Hi,
^^^ 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.
command in your shell before attempting the cloning -- this should
remove the upper limit on the
Hi,
Thanks for the reply.
Can you tell us what command you ran, and also try to get a readable
backtrace from your installation?
The crash is happening only when the users are trying to do a clone. I
was monitoring from the htop when triggering a clone operation, all
the cores of the
Hi,
I am using git with Gitlab/Gitolite configuration. Git version is
1.7.9.5 in Ubuntu 12.04. There has been a consistent git crash
recently and have attached the /var/crash/_usr_lib_git-core_
git.1001.crash file.
The crash output is pasted in the following link
http://pastebin.com/uAQS81BX
I
6 matches
Mail list logo