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
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
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.
--
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 t
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/16957668/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/16957669/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/16957670/Disassembly.txt
** Attachm
StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()
** Tags removed: need-i386-retrace
** Tags added: apport-failed-retrace
** Attachment added: "Stacktrace.txt (retraced)"
http://launchpadlibrarian.net/16957827/Stacktrace.txt
--
git crashed with SIGSEGV on ls-remote
https://bugs.launchpad.net/bug
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 t
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/16957668/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/16957669/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/16957670/Disassembly.txt
** Attachm
StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()
** Tags removed: need-i386-retrace
** Tags added: apport-failed-retrace
** Attachment added: "Stacktrace.txt (retraced)"
http://launchpadlibrarian.net/16957827/Stacktrace.txt
--
git crashed with SIGSEGV on ls-remote
https://bugs.launchpad.net/bug
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 t
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
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.
--
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
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
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.
--
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
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/16957668/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/16957669/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/16957670/Disassembly.txt
** Attachm
StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()
** Tags removed: need-i386-retrace
** Tags added: apport-failed-retrace
** Attachment added: "Stacktrace.txt (retraced)"
http://launchpadlibrarian.net/16957827/Stacktrace.txt
--
git crashed with SIGSEGV on ls-remote
https://bugs.launchpad.net/bug
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/16957668/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/16957669/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/16957670/Disassembly.txt
** Attachm
StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()
** Tags removed: need-i386-retrace
** Tags added: apport-failed-retrace
** Attachment added: "Stacktrace.txt (retraced)"
http://launchpadlibrarian.net/16957827/Stacktrace.txt
--
git crashed with SIGSEGV on ls-remote
https://bugs.launchpad.net/bug
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
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.
--
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/16957668/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/16957669/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/16957670/Disassembly.txt
** Attachm
StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()
** Tags removed: need-i386-retrace
** Tags added: apport-failed-retrace
** Attachment added: "Stacktrace.txt (retraced)"
http://launchpadlibrarian.net/16957827/Stacktrace.txt
--
git crashed with SIGSEGV on ls-remote
https://bugs.launchpad.net/bug
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
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 t
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
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.
--
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 t
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
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/16957668/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/16957669/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/16957670/Disassembly.txt
** Attachm
StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()
** Tags removed: need-i386-retrace
** Tags added: apport-failed-retrace
** Attachment added: "Stacktrace.txt (retraced)"
http://launchpadlibrarian.net/16957827/Stacktrace.txt
--
git crashed with SIGSEGV on ls-remote
https://bugs.launchpad.net/bug
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
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.
--
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
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 t
36 matches
Mail list logo
