Re: Git crash in Ubuntu 12.04

2013-04-24 Thread Sivaram Kannan
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  0x004820f0 in ?? ()
(gdb) bt
#0  0x004820f0 in ?? ()
#1  0x0044b3aa in ?? ()
#2  0x0044b641 in ?? ()
#3  0x7f077973de9a in start_thread (arg=0x7f0747fff700)
at pthread_create.c:308
#4  0x7f077946acbd in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:104
#5  0x in ?? ()
(gdb)

./Siva.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Git crash in Ubuntu 12.04

2013-04-19 Thread Duy Nguyen
On Thu, Apr 18, 2013 at 9:32 PM, Sivaram Kannan siva.de...@gmail.com 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 without symbols gives very
little information (at least for people who do not use Ubuntu).
--
Duy
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Git crash in Ubuntu 12.04

2013-04-18 Thread Sivaram Kannan
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.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Git crash in Ubuntu 12.04

2013-04-17 Thread Sivaram Kannan
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 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  0x0044bb77 in ?? ()
(gdb) bt
#0  0x0044bb77 in ?? ()
#1  0x0044cb54 in ?? ()
#2  0x0044d4f1 in ?? ()
#3  0x00405634 in ?? ()
#4  0x00404a30 in ?? ()
#5  0x7fe2a149876d 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  0x00404e65 in ?? ()
#7  0x7fffad58fb18 in ?? ()
#8  0x001c in ?? ()
#9  0x0007 in ?? ()
#10 0x7fffad591c95 in ?? ()
#11 0x7fffad591c99 in ?? ()
#12 0x7fffad591ca6 in ?? ()
#13 0x7fffad591cad in ?? ()
#14 0x7fffad591cb3 in ?? ()
#15 0x7fffad591cbc in ?? ()
#16 0x7fffad591cc7 in ?? ()
#17 0x in ?? ()

Thanks,
./Siva.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Git crash in Ubuntu 12.04

2013-04-17 Thread Duy Nguyen
On Wed, Apr 17, 2013 at 4:28 PM, Sivaram Kannan siva.de...@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
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Git crash in Ubuntu 12.04

2013-04-12 Thread Sivaram Kannan
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 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.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Git crash in Ubuntu 12.04

2013-04-12 Thread Konstantin Khomoutov
On Fri, 12 Apr 2013 18:58:24 +0530
Sivaram Kannan siva.de...@gmail.com 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 that easy to just get a plain old
coredump file -- see below.

  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
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Git crash in Ubuntu 12.04

2013-04-11 Thread Sivaram Kannan
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.

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

0040-00541000 r-xp  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  00:00 0
 01c13000-01ecf000 rw-p  00:00 0  [heap]
 7f1ad57c-7f1ae000 rw-p  00:00 0
 7f1ae000-7f1ae0ed4000 rw-p  00:00 0
 7f1ae0ed4000-7f1ae400 ---p  00:00 0
 7f1ae400-7f1ae665f000 rw-p  00:00 0
 7f1ae665f000-7f1ae800 ---p  00:00 0
 7f1ae800-7f1aea91a000 rw-p  00:00 0
 7f1aea91a000-7f1aec00 ---p  00:00 0
 7f1aec00-7f1aefede000 rw-p  00:00 0
 7f1aefede000-7f1af000 ---p  00:00 0
 7f1af000-7f1af3b95000 rw-p  00:00 0
 7f1af3b95000-7f1af400 ---p  00:00 0
 7f1af414b000-7f1af5eaf000 rw-p  00:00 0
 7f1af6c4d000-7f1af6ffe000 rw-p  00:00 0
 7f1af6ffe000-7f1af6fff000 ---p  00:00 0
 7f1af6fff000-7f1af77ff000 rw-p  00:00 0
 7f1af77ff000-7f1af780 ---p  00:00 0
 7f1af780-7f1af800 rw-p  00:00 0
 7f1af800-7f1afb9cf000 rw-p  00:00 0
 7f1afb9cf000-7f1afc00 ---p  00:00 0
 7f1afc113000-7f1afc114000 ---p  00:00 0
 7f1afc114000-7f1afc914000 rw-p  00:00 0
 7f1afc914000-7f1afc915000 ---p  00:00 0
 7f1afc915000-7f1afd115000 rw-p  00:00 0
 7f1afd115000-7f1afe147000 r--p  fc:00 13371109
   
/home/git/repositories/sggroup/storegrid.git/objects/pack/pack-a72ab4cf996276ca527a26c6711414e97828aa01.pack
 7f1afe147000-7f1afe52d000 rw-p  00:00 0
 7f1afe8ad000-7f1afe92e000 rw-p  00:00 0
 7f1afe92e000-7f1afea57000 r--p  fc:00 13371175
   
/home/git/repositories/sggroup/storegrid.git/objects/pack/pack-725eb21535f4d3782dce7c1f163c535ae46dd7a3.pack
 7f1afea57000-7f1afeaab000 r--p  fc:00 13371183
   
/home/git/repositories/sggroup/storegrid.git/objects/pack/pack-a242e26dd75d9f94ac7cc021b79b5a23be86f772.pack
 7f1afeaab000-7f1afeb2d000 r--p  fc:00 13371188
   
/home/git/repositories/sggroup/storegrid.git/objects/pack/pack-8df0b1d878ce57e7b81439bfbbed75da58298d4f.pack
 7f1afeb2d000-7f1afed1c000 r--p  fc:00 13371200
   
/home/git/repositories/sggroup/storegrid.git/objects/pack/pack-e7279a5e263e36487664846efd3cf8e326e28b52.pack
 7f1afed1c000-7f1afee48000 r--p  fc:00 13371324
   
/home/git/repositories/sggroup/storegrid.git/objects/pack/pack-b9440d0950347a7f42994eecb3e4b96ac6cba2ef.pack
 7f1afee48000-7f1afef23000 r--p  fc:00 13371272
   
/home/git/repositories/sggroup/storegrid.git/objects/pack/pack-334b5d2e30e802e8d11095d64348c61a6fabf4ab.pack
 7f1afef23000-7f1b0028 r--p  fc:00 13371511
   
/home/git/repositories/sggroup/storegrid.git/objects/pack/pack-89264699af6b413cbcba76e68866a9531693dc2e.pack
 7f1b0028-7f1b00391000 r--p  fc:00 13372427
   
/home/git/repositories/sggroup/storegrid.git/objects/pack/pack-c7d9d3af8fb96dd231186fcdb08c451e0aba3cc2.pack
 

Re: Git crash in Ubuntu 12.04

2013-04-11 Thread Konstantin Khomoutov
On Thu, 11 Apr 2013 15:50:31 +0530
Sivaram Kannan siva.de...@gmail.com 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 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...
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Git crash in Ubuntu 12.04

2013-04-10 Thread Sivaram Kannan
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.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Git crash in Ubuntu 12.04

2013-04-10 Thread Thomas Rast
Sivaram Kannan siva.de...@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
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html