From: Thomas Rast <trast@inf.ethz.ch>
To: Sivaram Kannan <siva.devel@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Git crash in Ubuntu 12.04
Date: Wed, 10 Apr 2013 09:44:29 +0200 [thread overview]
Message-ID: <87mwt6ltia.fsf@linux-k42r.v.cablecom.net> (raw)
In-Reply-To: <CAJiNi_FfU9Gsr2D9CcC0wWwgO1oKBXwxp87-wBUJBU2kyGaQNQ@mail.gmail.com> (Sivaram Kannan's message of "Wed, 10 Apr 2013 12:11:46 +0530")
Sivaram Kannan <siva.devel@gmail.com> 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 link
>
> http://pastebin.com/uAQS81BX
>
> I removed some long binary information at the end of the file as
> pastebin does not allow more than 500k pasting. The crash is
> consistently happening and I am planning on for a debian deployment of
> gitlab.
Can you tell us what command you ran, and also try to get a readable
backtrace from your installation?
It seems that the paste would have contained a core dump (you snipped
it9, but it would be pretty useless without the corresponding binary
anyway. Once you have the coredump in hand (as a file) you can use
gdb $(which git) the_coredump_file
and then in the GDB prompt, enter 'backtrace' and paste its output, to
give us an idea what is going on.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2013-04-10 7:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 6:41 Git crash in Ubuntu 12.04 Sivaram Kannan
2013-04-10 7:44 ` Thomas Rast [this message]
2013-04-11 10:20 ` Sivaram Kannan
2013-04-11 13:06 ` Konstantin Khomoutov
2013-04-12 13:28 ` Sivaram Kannan
2013-04-12 14:05 ` Konstantin Khomoutov
2013-04-17 6:28 ` Sivaram Kannan
2013-04-17 7:26 ` Duy Nguyen
2013-04-18 11:32 ` Sivaram Kannan
2013-04-18 15:16 ` Sivaram Kannan
2013-04-19 7:53 ` Thomas Rast
2013-04-19 8:48 ` Duy Nguyen
2013-04-24 14:51 ` Sivaram Kannan
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=87mwt6ltia.fsf@linux-k42r.v.cablecom.net \
--to=trast@inf.ethz.ch \
--cc=git@vger.kernel.org \
--cc=siva.devel@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.