threads / discuss / 33454

Git crash in Ubuntu 12.04

Subject: Git crash in Ubuntu 12.04

## tl;dr

13 messages between Apr 10, 2013 and Apr 24, 2013.

replies: 12people: 4as markdown or json

Sivaram Kannan· Apr 10, 2013, 06:41 UTC · lore
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.

Please advice what could I do to solve this problem.
./Siva.
Thomas Rast· Apr 10, 2013, 07:44 UTC · re: Sivaram Kannan · lore

Re: Git crash in Ubuntu 12.04

Sivaram Kannan <siva.devel@gmail.com> writes:
Show 15 quoted lines
> 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
Sivaram Kannan· Apr 11, 2013, 10:20 UTC · re: Thomas Rast · lore

Re: Git crash in Ubuntu 12.04

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 processor hits 100% for some time before dropping. The servers hw config is Intel Quad core processor with 8GB Ram.

Show 9 quoted lines
> 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.
>
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 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.launchpad.net/gdb-linaro/>...
Reading symbols from /usr/bin/git...(no debugging symbols found)...done.
BFD: Warning: /var/crash/dump/CoreDump is truncated: expected core
file size >= 600195072, found: 1114112.
[New LWP 17584]
[New LWP 17587]
[New LWP 17586]
[New LWP 17440]
[New LWP 17585]
Cannot access memory at address 0x7f193623e2a8
Cannot access memory at address 0x7f193623e2a0
(gdb) bt
#0  0x00000000004820f0 in ?? ()
Cannot access memory at address 0x7f191073bda8
(gdb)
=========

The following I am copy pasting from the file called ProcMaps, which gets created after I run apport-unpack <crashfile>.

00400000-00541000 r-xp 00000000 fc:00 2098029
  /usr/lib/git-core/git
 00741000-00742000 r--p 00141000 fc:00 2098029
   /usr/lib/git-core/git
 00742000-00749000 rw-p 00142000 fc:00 2098029
   /usr/lib/git-core/git
 00749000-00799000 rw-p 00000000 00:00 0
 01c13000-01ecf000 rw-p 00000000 00:00 0                                  [heap]
 7f1ad57c0000-7f1ae0000000 rw-p 00000000 00:00 0
 7f1ae0000000-7f1ae0ed4000 rw-p 00000000 00:00 0
 7f1ae0ed4000-7f1ae4000000 ---p 00000000 00:00 0
 7f1ae4000000-7f1ae665f000 rw-p 00000000 00:00 0
 7f1ae665f000-7f1ae8000000 ---p 00000000 00:00 0
 7f1ae8000000-7f1aea91a000 rw-p 00000000 00:00 0
 7f1aea91a000-7f1aec000000 ---p 00000000 00:00 0
 7f1aec000000-7f1aefede000 rw-p 00000000 00:00 0
 7f1aefede000-7f1af0000000 ---p 00000000 00:00 0
 7f1af0000000-7f1af3b95000 rw-p 00000000 00:00 0
 7f1af3b95000-7f1af4000000 ---p 00000000 00:00 0
 7f1af414b000-7f1af5eaf000 rw-p 00000000 00:00 0
 7f1af6c4d000-7f1af6ffe000 rw-p 00000000 00:00 0
 7f1af6ffe000-7f1af6fff000 ---p 00000000 00:00 0
 7f1af6fff000-7f1af77ff000 rw-p 00000000 00:00 0
 7f1af77ff000-7f1af7800000 ---p 00000000 00:00 0
 7f1af7800000-7f1af8000000 rw-p 00000000 00:00 0
 7f1af8000000-7f1afb9cf000 rw-p 00000000 00:00 0
 7f1afb9cf000-7f1afc000000 ---p 00000000 00:00 0
 7f1afc113000-7f1afc114000 ---p 00000000 00:00 0
 7f1afc114000-7f1afc914000 rw-p 00000000 00:00 0
 7f1afc914000-7f1afc915000 ---p 00000000 00:00 0
 7f1afc915000-7f1afd115000 rw-p 00000000 00:00 0
 7f1afd115000-7f1afe147000 r--p 00000000 fc:00 13371109
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-a72ab4cf996276ca527a26c6711414e97828aa01.pack
 7f1afe147000-7f1afe52d000 rw-p 00000000 00:00 0
 7f1afe8ad000-7f1afe92e000 rw-p 00000000 00:00 0
 7f1afe92e000-7f1afea57000 r--p 00000000 fc:00 13371175
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-725eb21535f4d3782dce7c1f163c535ae46dd7a3.pack
 7f1afea57000-7f1afeaab000 r--p 00000000 fc:00 13371183
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-a242e26dd75d9f94ac7cc021b79b5a23be86f772.pack
 7f1afeaab000-7f1afeb2d000 r--p 00000000 fc:00 13371188
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-8df0b1d878ce57e7b81439bfbbed75da58298d4f.pack
 7f1afeb2d000-7f1afed1c000 r--p 00000000 fc:00 13371200
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-e7279a5e263e36487664846efd3cf8e326e28b52.pack
 7f1afed1c000-7f1afee48000 r--p 00000000 fc:00 13371324
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-b9440d0950347a7f42994eecb3e4b96ac6cba2ef.pack
 7f1afee48000-7f1afef23000 r--p 00000000 fc:00 13371272
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-334b5d2e30e802e8d11095d64348c61a6fabf4ab.pack
 7f1afef23000-7f1b00280000 r--p 00000000 fc:00 13371511
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-89264699af6b413cbcba76e68866a9531693dc2e.pack
 7f1b00280000-7f1b00391000 r--p 00000000 fc:00 13372427
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-c7d9d3af8fb96dd231186fcdb08c451e0aba3cc2.pack
 7f1b00391000-7f1b003fa000 r--p 00000000 fc:00 13372643
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-f5fcf2f514ee6233964234e7d5947f03013b6b21.pack
 7f1b003fa000-7f1b02efe000 r--p 00000000 fc:00 13372753
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-dfb6ee684e3f58549254a7ddb18776670f64b8f5.pack
 7f1b02efe000-7f1b049e4000 r--p 00000000 fc:00 13371038
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-08a676f6ba45b69cd2a19a7d9f626bd24d9a7c6a.pack
 7f1b049e4000-7f1b049ec000 r--p 00000000 fc:00 13371071
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-075a4d75da5f11b72a3a9a68cb1e6209efe1080b.pack
 7f1b049ec000-7f1b0a3fd000 r--p 00000000 fc:00 13371039
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-8c618ce37614112a933a2dd02bfc4095813f9912.pack
 7f1b0a3fd000-7f1b0a64b000 r--p 00000000 fc:00 13371075
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-af68425c69ab8a50a8e6bb58e13d742f8b5d5edd.pack
 7f1b0a67c000-7f1b0a67d000 rw-p 00000000 00:00 0
 7f1b0a67d000-7f1b0a814000 r--p 00000000 fc:00 13372807
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-7067e4bd2b58f72bcb1a88a3df35cee5cc429090.pack
 7f1b0a814000-7f1b13509000 r--p 00000000 fc:00 13370795
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-61336138de0ccbe951b4652f43d7bbd087edb380.pack
 7f1b13509000-7f1b2604f000 r--p 00000000 fc:00 13370792
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-04da49cd5676b94d557fe984d9a844c1eae94477.pack
 7f1b2604f000-7f1b2623b000 r--p 00000000 fc:00 13371128
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-d79143b52a19edf04d485434f10663ccbb9eee88.pack
 7f1b2623b000-7f1b2629f000 r--p 00000000 fc:00 13370793
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-04da49cd5676b94d557fe984d9a844c1eae94477.idx
 7f1b2629f000-7f1b262a4000 r--p 00000000 fc:00 13371117
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-a72ab4cf996276ca527a26c6711414e97828aa01.idx
 7f1b262a4000-7f1b262a8000 r--p 00000000 fc:00 13371178
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-725eb21535f4d3782dce7c1f163c535ae46dd7a3.idx
 7f1b262a8000-7f1b262ab000 r--p 00000000 fc:00 13371184
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-a242e26dd75d9f94ac7cc021b79b5a23be86f772.idx
 7f1b262ab000-7f1b262af000 r--p 00000000 fc:00 13371189
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-8df0b1d878ce57e7b81439bfbbed75da58298d4f.idx
 7f1b262af000-7f1b262b3000 r--p 00000000 fc:00 13371202
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-e7279a5e263e36487664846efd3cf8e326e28b52.idx
 7f1b262b3000-7f1b262b6000 r--p 00000000 fc:00 13371277
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-334b5d2e30e802e8d11095d64348c61a6fabf4ab.idx
 7f1b262b6000-7f1b262b9000 r--p 00000000 fc:00 13371325
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-b9440d0950347a7f42994eecb3e4b96ac6cba2ef.idx
 7f1b262b9000-7f1b262bb000 r--p 00000000 fc:00 13372359
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-89264699af6b413cbcba76e68866a9531693dc2e.idx
 7f1b262bb000-7f1b262bd000 r--p 00000000 fc:00 13372428
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-c7d9d3af8fb96dd231186fcdb08c451e0aba3cc2.idx
 7f1b262bd000-7f1b262c0000 r--p 00000000 fc:00 13372645
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-f5fcf2f514ee6233964234e7d5947f03013b6b21.idx
 7f1b262c0000-7f1b262c2000 r--p 00000000 fc:00 13372762
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-dfb6ee684e3f58549254a7ddb18776670f64b8f5.idx
 7f1b262c2000-7f1b262c5000 r--p 00000000 fc:00 13372809
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-7067e4bd2b58f72bcb1a88a3df35cee5cc429090.idx
 7f1b262c5000-7f1b262f2000 r--p 00000000 fc:00 13371005
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-61336138de0ccbe951b4652f43d7bbd087edb380.idx
 7f1b262f2000-7f1b262f6000 r--p 00000000 fc:00 13371043
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-08a676f6ba45b69cd2a19a7d9f626bd24d9a7c6a.idx
 7f1b262f6000-7f1b262f9000 r--p 00000000 fc:00 13371072
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-075a4d75da5f11b72a3a9a68cb1e6209efe1080b.idx
 7f1b262f9000-7f1b262fb000 r--p 00000000 fc:00 13371073
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-8c618ce37614112a933a2dd02bfc4095813f9912.idx
 7f1b262fb000-7f1b26300000 r--p 00000000 fc:00 13371076
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-af68425c69ab8a50a8e6bb58e13d742f8b5d5edd.idx
 7f1b26300000-7f1b26306000 r--p 00000000 fc:00 13371129
   /home/git/repositories/sggroup/storegrid.git/objects/pack/pack-d79143b52a19edf04d485434f10663ccbb9eee88.idx
 7f1b26306000-7f1b265cf000 r--p 00000000 fc:00 530936
   /usr/lib/locale/locale-archive
 7f1b265cf000-7f1b26784000 r-xp 00000000 fc:00 18616016
   /lib/x86_64-linux-gnu/libc-2.15.so
 7f1b26784000-7f1b26983000 ---p 001b5000 fc:00 18616016
   /lib/x86_64-linux-gnu/libc-2.15.so
 7f1b26983000-7f1b26987000 r--p 001b4000 fc:00 18616016
   /lib/x86_64-linux-gnu/libc-2.15.so
 7f1b26987000-7f1b26989000 rw-p 001b8000 fc:00 18616016
   /lib/x86_64-linux-gnu/libc-2.15.so
 7f1b26989000-7f1b2698e000 rw-p 00000000 00:00 0
 7f1b2698e000-7f1b269a6000 r-xp 00000000 fc:00 18616018
   /lib/x86_64-linux-gnu/libpthread-2.15.so
 7f1b269a6000-7f1b26ba5000 ---p 00018000 fc:00 18616018
   /lib/x86_64-linux-gnu/libpthread-2.15.so
 7f1b26ba5000-7f1b26ba6000 r--p 00017000 fc:00 18616018
   /lib/x86_64-linux-gnu/libpthread-2.15.so
 7f1b26ba6000-7f1b26ba7000 rw-p 00018000 fc:00 18616018
   /lib/x86_64-linux-gnu/libpthread-2.15.so
 7f1b26ba7000-7f1b26bab000 rw-p 00000000 00:00 0
 7f1b26bab000-7f1b26bc3000 r-xp 00000000 fc:00 18616021
   /lib/x86_64-linux-gnu/libresolv-2.15.so
 7f1b26bc3000-7f1b26dc3000 ---p 00018000 fc:00 18616021
   /lib/x86_64-linux-gnu/libresolv-2.15.so
 7f1b26dc3000-7f1b26dc4000 r--p 00018000 fc:00 18616021
   /lib/x86_64-linux-gnu/libresolv-2.15.so
 7f1b26dc4000-7f1b26dc5000 rw-p 00019000 fc:00 18616021
   /lib/x86_64-linux-gnu/libresolv-2.15.so
 7f1b26dc5000-7f1b26dc7000 rw-p 00000000 00:00 0
 7f1b26dc7000-7f1b26ddd000 r-xp 00000000 fc:00 18612452
   /lib/x86_64-linux-gnu/libz.so.1.2.3.4
 7f1b26ddd000-7f1b26fdc000 ---p 00016000 fc:00 18612452
   /lib/x86_64-linux-gnu/libz.so.1.2.3.4
 7f1b26fdc000-7f1b26fdd000 r--p 00015000 fc:00 18612452
   /lib/x86_64-linux-gnu/libz.so.1.2.3.4
 7f1b26fdd000-7f1b26fde000 rw-p 00016000 fc:00 18612452
   /lib/x86_64-linux-gnu/libz.so.1.2.3.4
 7f1b26fde000-7f1b27000000 r-xp 00000000 fc:00 18616030
   /lib/x86_64-linux-gnu/ld-2.15.so
 7f1b271f3000-7f1b271f7000 rw-p 00000000 00:00 0
 7f1b271fe000-7f1b27200000 rw-p 00000000 00:00 0
 7f1b27200000-7f1b27201000 r--p 00022000 fc:00 18616030
   /lib/x86_64-linux-gnu/ld-2.15.so
 7f1b27201000-7f1b27203000 rw-p 00023000 fc:00 18616030
   /lib/x86_64-linux-gnu/ld-2.15.so
 7fff63db5000-7fff63dd6000 rw-p 00000000 00:00 0
   [stack]
 7fff63dff000-7fff63e00000 r-xp 00000000 00:00 0                          [vdso]
 ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0
   [vsyscall]
Konstantin Khomoutov· Apr 11, 2013, 13:06 UTC · re: Sivaram Kannan · lore

Re: Git crash in Ubuntu 12.04

On Thu, 11 Apr 2013 15:50:31 +0530 Sivaram Kannan <siva.devel@gmail.com> wrote:

[...]
Show 15 quoted lines
> 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 or later
> <http://gnu.org/licenses/gpl.html> This is free software: you are
> free to change and redistribute it. There is NO WARRANTY, to the
> extent permitted by law.  Type "show copying" and "show warranty" for
> details. This GDB was configured as "x86_64-linux-gnu".
> For bug reporting instructions, please see:
> <http://bugs.launchpad.net/gdb-linaro/>...
> Reading symbols from /usr/bin/git...(no debugging symbols
> found)...done. BFD: Warning: /var/crash/dump/CoreDump is truncated:
> expected core file size >= 600195072, found: 1114112.
^^^ Try to issue the
$ ulimit -c unlimited

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...

Sivaram Kannan· Apr 12, 2013, 13:28 UTC · re: Konstantin Khomoutov · lore

Re: Git crash in Ubuntu 12.04

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.

Show 5 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? Would upgrading to the 1.8.2.1 - latest in Ubuntu PPA would help?

./Siva.
Konstantin Khomoutov· Apr 12, 2013, 14:05 UTC · re: Sivaram Kannan · lore

Re: Git crash in Ubuntu 12.04

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
Sivaram Kannan· Apr 17, 2013, 06:28 UTC · re: Konstantin Khomoutov · lore

Re: Git crash in Ubuntu 12.04

Hi,
Show 9 quoted lines
>> > $ 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 from git this time. See whether it helps. I have setup another machine with Ubuntu 12.04 and updated only git and ported the repo there, after 200 clones no crash so far. Mostly will be moving latest repo to that server to solve this issue.

gitadmin@gitserver:/var/crash/gitcash$ 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 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://bugs.launchpad.net/gdb-linaro/>... Reading symbols from /usr/bin/git...(no debugging symbols found)...done. [New LWP 12823]

warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `git pack-objects --revs --all --stdout
--progress --delta-base-offset'.
Program terminated with signal 11, Segmentation fault.
#0  0x000000000044bb77 in ?? ()
(gdb) bt
#0  0x000000000044bb77 in ?? ()
#1  0x000000000044cb54 in ?? ()
#2  0x000000000044d4f1 in ?? ()
#3  0x0000000000405634 in ?? ()
#4  0x0000000000404a30 in ?? ()
#5  0x00007fe2a149876d in __libc_start_main (main=0x404980, argc=7,
ubp_av=0x7fffad58fb28, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>,
    stack_end=0x7fffad58fb18) at libc-start.c:226
#6  0x0000000000404e65 in ?? ()
#7  0x00007fffad58fb18 in ?? ()
#8  0x000000000000001c in ?? ()
#9  0x0000000000000007 in ?? ()
#10 0x00007fffad591c95 in ?? ()
#11 0x00007fffad591c99 in ?? ()
#12 0x00007fffad591ca6 in ?? ()
#13 0x00007fffad591cad in ?? ()
#14 0x00007fffad591cb3 in ?? ()
#15 0x00007fffad591cbc in ?? ()
#16 0x00007fffad591cc7 in ?? ()
#17 0x0000000000000000 in ?? ()

Thanks, ./Siva.

Duy Nguyen· Apr 17, 2013, 07:26 UTC · re: Sivaram Kannan · lore

Re: Git crash in Ubuntu 12.04

On Wed, Apr 17, 2013 at 4:28 PM, Sivaram Kannan <siva.devel@gmail.com> 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
> ported the repo there, after 200 clones no crash so far.

Any chance you could publish the repository that causes the crash? -- Duy

Sivaram Kannan· Apr 18, 2013, 11:32 UTC · re: Duy Nguyen · lore

Re: Git crash in Ubuntu 12.04

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 the repo online. But I am willing to try any steps on the repo to get more info. Most likely I would restore the latest repo to the stanby server I tested which works with any crash. Let me know what I can do to get more information.

./Siva.
Sivaram Kannan· Apr 18, 2013, 15:16 UTC · re: Sivaram Kannan · lore

Re: Git crash in Ubuntu 12.04

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 origin
* remote origin
  Fetch URL: git@gitserver:sggroup/sgrid.git
  Push  URL: git@gitserver:sggroup/sgrid.git
  HEAD branch: master
  Remote branches:
    SGRID_5_5_0_BRANCH                 tracked
    master                                 tracked
    refs/remotes/origin/4_4_Release_Branch stale (use 'git remote prune' to remo
ve)
  Local branch configured for 'git pull':
    4_4_Release_Branch merges with remote 4_4_Release_Branch

Thanks, ./Siva.

On Thu, Apr 18, 2013 at 5:02 PM, Sivaram Kannan <siva.devel@gmail.com> wrote:
Show 19 quoted lines
> 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 the repo online. But I am willing to try
> any steps on the repo to get more info. Most likely I would restore
> the latest repo to the stanby server I tested which works with any
> crash. Let me know what I can do to get more information.
>
> ./Siva.
Thomas Rast· Apr 19, 2013, 07:53 UTC · re: Sivaram Kannan · lore

Re: Git crash in Ubuntu 12.04

Sivaram Kannan <siva.devel@gmail.com> writes:
Show 6 quoted lines
> 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??

By commit, do you mean push? I.e., something crashed while a push was going on?

The recovery strategy depends a lot on how valuable/recoverable the work that happened since the last backup was, but restoring from backup, running 'git fsck' on all involved repos (including devs' workstations!) and then having the devs re-push what they had locally seems like a good strategy to me.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch
Duy Nguyen· Apr 19, 2013, 08:48 UTC · re: Sivaram Kannan · lore

Re: Git crash in Ubuntu 12.04

On Thu, Apr 18, 2013 at 9:32 PM, Sivaram Kannan <siva.devel@gmail.com> wrote:
Show 7 quoted lines
> 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 without symbols gives very little information (at least for people who do not use Ubuntu). -- Duy

Sivaram Kannan· Apr 24, 2013, 14:51 UTC · re: Duy Nguyen · lore

Re: Git crash in Ubuntu 12.04

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 gives very
> little information (at least for people who do not use Ubuntu).

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 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://bugs.launchpad.net/gdb-linaro/>. Reading symbols from /tmp/tmp6_sJPS/usr/lib/git-core/git...(no debugging symbols found)...done. [New LWP 31469] [New LWP 31468] [New LWP 31466] [New LWP 31464] [New LWP 31467] warning: Can't read pathname for load map: Input/output error. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". warning: the debug information found in "/tmp/tmp6_sJPS/usr/lib/debug//lib/x86_64-linux-gnu/ld-2.15.so" does not match "/tmp/tmp6_sJPS/lib64/ld-linux-x86-64.so.2" (CRC mismatch).

Core was generated by `git pack-objects --revs --all --stdout
--delta-base-offset'.
Program terminated with signal 11, Segmentation fault.
#0  0x00000000004820f0 in ?? ()
(gdb) bt
#0  0x00000000004820f0 in ?? ()
#1  0x000000000044b3aa in ?? ()
#2  0x000000000044b641 in ?? ()
#3  0x00007f077973de9a in start_thread (arg=0x7f0747fff700)
    at pthread_create.c:308
#4  0x00007f077946acbd in clone ()
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S:104
#5  0x0000000000000000 in ?? ()
(gdb)
./Siva.

← back to recent threads