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
On Thu, Apr 18, 2013 at 9:32 PM, Sivaram Kannan wrote:
> 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?
Yes. Please do. The reason is a backtrace
Sivaram Kannan writes:
> Hi,
>
> The git crashed during one of the commits by a developer I think, the
> remote is not even showing the working branch. The local branch of is
> all right, but the remote repo is corrupted and could not git fsck
> also. Is restoring the last night's backup is my on
Hi,
The git crashed during one of the commits by a developer I think, the
remote is not even showing the working branch. The local branch of is
all right, but the remote repo is corrupted and could not git fsck
also. Is restoring the last night's backup is my only option??
$ git remote show origi
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 publi
On Wed, Apr 17, 2013 at 4:28 PM, Sivaram Kannan wrote:
> Got an proper dump from git this time. See whether it helps.
Probably not because there are no debugging symbols. Not sure how
ubuntu packages these symbols..
> I have setup another machine with Ubuntu 12.04 and updated only git and
> port
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 p
On Fri, 12 Apr 2013 18:58:24 +0530
Sivaram Kannan 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
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 t
On Thu, 11 Apr 2013 15:50:31 +0530
Sivaram Kannan wrote:
[...]
> Output of coredump gdb:
>
> gitadmin@gitserver:/var/crash/dump$ gdb git CoreDump
> GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04
> Copyright (C) 2012 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 o
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 proce
Sivaram Kannan writes:
> 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
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
13 matches
Mail list logo
