git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git crash in Ubuntu 12.04

From
KKKonstantin Khomoutov <flatworm@users.sourceforge.net>
Date
Apr 12, 2013, 14:05 UTC
Message-ID
<20130412180525.aa5b8eacd691a427244d6ab5@domain007.com>
In-Reply-To
<CAJiNi_Gju2aJkVJJmoxnEAubfPvjaVhVF6DisaLn5kUJ3YRD=w@mail.gmail.com>

On Fri, 12 Apr 2013 18:58:24 +0530 Sivaram Kannan <siva.devel@gmail.com> wrote:

Show 7 quoted lines
> > ^^^ 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.

Show 9 quoted lines
> > 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" [1].

Considering this, I would try to explore two routes:
* [1] 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 1.8.2.1 - 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.

1. https://wiki.ubuntu.com/Apport
Previous: Sivaram KannanNext: Sivaram Kannan
Message 6 of 13 in “Git crash in Ubuntu 12.04”
  1. Sivaram KannanApr 10, 2013
  2. Thomas RastApr 10, 2013
  3. Sivaram KannanApr 11, 2013
  4. Konstantin KhomoutovApr 11, 2013
  5. Sivaram KannanApr 12, 2013
  6. Konstantin KhomoutovApr 12, 2013
  7. Sivaram KannanApr 17, 2013
  8. Duy NguyenApr 17, 2013
  9. Sivaram KannanApr 18, 2013
  10. Sivaram KannanApr 18, 2013
  11. Thomas RastApr 19, 2013
  12. Duy NguyenApr 19, 2013
  13. Sivaram KannanApr 24, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.