git crashed with SIGSEGV on ls-remote

Bug #259752 reported by Andreas Moog
18
Affects Status Importance Assigned to Milestone
git-core (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: git-core

The following produces a segfault:

git ls-remote http://git.o-hand.com/thomas/git/phone.git master

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/git
NonfreeKernelModules: nvidia
Package: git-core 1:1.5.4.3-1ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: git ls-remote http://git.o-hand.com/thomas/git/phone.git master
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: git-core
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: git crashed with SIGSEGV
Uname: Linux 2.6.26-5-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Revision history for this message
Andreas Moog (ampelbein) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

 Thank you for taking the time to report this bug and helping to make Ubuntu better.

However, processing it in order to get sufficient information for the developers failed (it does not generate an useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report. Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

Changed in git-core:
status: New → Invalid
Revision history for this message
Caspar Clemens Mierau (leitmedium) wrote :

Hi,

I can reproduce this on an up to date Hardy. The segmentation faults happens before any real http action, therefore it's unimportant, which http url is used (existing or unknown hosts).

I tried to get a verbose backtrace, but I mostly get "no symbol" messages, though I install git-dbgsym and libcurl3-dbg. If you have any hints on getting a more detailed backtrace by installing specific packages, let me know.

Changed in git-core:
status: Invalid → Incomplete
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Thank you, Caspar Clemens, for your reply. In the backtrace itself there are information about what debug symbols need to be installed. Please attach it and I will have a look at it. Since you get an segmentation fault, a https://wiki.ubuntu.com/Valgrind would also be great. Thanks in advance.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in git-core (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.