| Summary: | [abrt] git-1.7.6.4-1.fc15: write_one: Process /usr/libexec/git-core/git was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Cesar Eduardo Barros <cesarb> | ||||
| Component: | git | Assignee: | Chris Wright <chrisw> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 15 | CC: | atkac, bkearney, chrisw, npajkovs, tmz | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:04b691cffe2ce504efec2431ae8f8bfd5853f2c1 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-08-07 15:41:30 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Cesar Eduardo Barros
2011-11-19 00:00:24 UTC
Created attachment 534520 [details]
File: backtrace
Attaching to a running instance with gdb, I can get more information:
(gdb) cont
Continuing.
[New Thread 0x7faa3fb9e700 (LWP 26124)]
[New Thread 0x7faa3f39d700 (LWP 26125)]
[New Thread 0x7faa3eb9c700 (LWP 26126)]
[New Thread 0x7faa3e39b700 (LWP 26127)]
[Thread 0x7faa3eb9c700 (LWP 26126) exited]
[Thread 0x7faa3e39b700 (LWP 26127) exited]
[Thread 0x7faa3f39d700 (LWP 26125) exited]
[Thread 0x7faa3fb9e700 (LWP 26124) exited]
Program received signal SIGSEGV, Segmentation fault.
0x0000000000447ecb in write_one (f=0x652ab70, e=0x7faa440bc248,
offset=0x7fffaaada1e8) at builtin/pack-objects.c:418
418 if (e->delta && !write_one(f, e->delta, offset))
The variable is valid at this point:
(gdb) print e
$1 = (struct object_entry *) 0x7faa440bc248
(gdb) print *e
$2 = {idx = {
sha1 = "\257>J\241)\266\023\064\a\342J\320\375ӆ\262M\245", <incomplete sequence \356>, crc32 = 0, offset = 0}, size = 20, in_pack = 0x1b15580,
in_pack_offset = 231061238, delta = 0x7faa440fbd58,
delta_child = 0x7faa440fbd58, delta_sibling = 0x7faa4436da50,
delta_data = 0x0, delta_size = 20, z_delta_size = 0, hash = 2099915708,
type = OBJ_OFS_DELTA, in_pack_type = OBJ_OFS_DELTA,
in_pack_header_size = 5 '\005', preferred_base = 0 '\000',
no_try_delta = 0 '\000'}
And the SEGV was at a call instruction:
(gdb) disassemble
Dump of assembler code for function write_one:
[...]
0x0000000000447ec9 <+73>: je 0x447ed8 <write_one+88>
=> 0x0000000000447ecb <+75>: callq 0x447e80 <write_one>
0x0000000000447ed0 <+80>: test %eax,%eax
The problem seems to be a stack overflow:
(gdb) info registers
rax 0x0 0
rbx 0x7faa440bc248 140369262789192
rcx 0x505eae 5267118
rdx 0x7fffaaada1e8 140736056893928
rsi 0x7faa440fbd58 140369263050072
rdi 0x652ab70 106081136
rbp 0x762e 0x762e
rsp 0x7fffaa2dcfa0 0x7fffaa2dcfa0
r8 0x10 16
r9 0x4e7c2d 5143597
r10 0x762e 30254
r11 0x64 100
r12 0x652ab70 106081136
r13 0x7fffaaada1e8 140736056893928
r14 0x0 0
r15 0x19d6 6614
rip 0x447ecb 0x447ecb <write_one+75>
eflags 0x10202 [ IF RF ]
cs 0x33 51
ss 0x2b 43
ds 0x0 0
es 0x0 0
fs 0x0 0
gs 0x0 0
%rsp is pointing outside the stack:
7faa6671a000-7faa6671b000 rw-p 00000000 00:00 0
7fffaa2de000-7fffaaadd000 rw-p 00000000 00:00 0 [stack]
7fffaabff000-7fffaac00000 r-xp 00000000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
The stack limit on this machine is 8M:
$ ulimit -s
8192
Here are the last few frames on the stack:
(gdb) where
#0 0x0000000000447ecb in write_one (f=0x652ab70, e=0x7faa440bc248,
offset=0x7fffaaada1e8) at builtin/pack-objects.c:418
#1 0x0000000000447ed0 in write_one (f=0x652ab70, e=0x7faa440fbd58,
offset=0x7fffaaada1e8) at builtin/pack-objects.c:418
#2 0x0000000000447ed0 in write_one (f=0x652ab70, e=0x7faa440bc248,
offset=0x7fffaaada1e8) at builtin/pack-objects.c:418
#3 0x0000000000447ed0 in write_one (f=0x652ab70, e=0x7faa440fbd58,
offset=0x7fffaaada1e8) at builtin/pack-objects.c:418
#4 0x0000000000447ed0 in write_one (f=0x652ab70, e=0x7faa440bc248,
offset=0x7fffaaada1e8) at builtin/pack-objects.c:418
#5 0x0000000000447ed0 in write_one (f=0x652ab70, e=0x7faa440fbd58,
offset=0x7fffaaada1e8) at builtin/pack-objects.c:418
#6 0x0000000000447ed0 in write_one (f=0x652ab70, e=0x7faa440bc248,
offset=0x7fffaaada1e8) at builtin/pack-objects.c:418
#7 0x0000000000447ed0 in write_one (f=0x652ab70, e=0x7faa440fbd58,
offset=0x7fffaaada1e8) at builtin/pack-objects.c:418
#8 0x0000000000447ed0 in write_one (f=0x652ab70, e=0x7faa440bc248,
offset=0x7fffaaada1e8) at builtin/pack-objects.c:418
#9 0x0000000000447ed0 in write_one (f=0x652ab70, e=0x7faa440fbd58,
offset=0x7fffaaada1e8) at builtin/pack-objects.c:418
#10 0x0000000000447ed0 in write_one (f=0x652ab70, e=0x7faa440bc248,
offset=0x7fffaaada1e8) at builtin/pack-objects.c:418
#11 0x0000000000447ed0 in write_one (f=0x652ab70, e=0x7faa440fbd58,
---Type <return> to continue, or q <return> to quit---
It seems to be caught in an endless recursive call.
I will check later with latest upstream git and see what happens. If it still breaks, I will report it upstream and close this bug.
I reported it upstream at http://article.gmane.org/gmane.comp.version-control.git/185708, and Junio answered at http://article.gmane.org/gmane.comp.version-control.git/185710 saying that the patch at http://article.gmane.org/gmane.comp.version-control.git/185573 would fix it. As I mention at http://article.gmane.org/gmane.comp.version-control.git/185711, it worked. So, this bug could be fixed by backporting that patch. See also the related patch at http://thread.gmane.org/gmane.comp.version-control.git/185574. This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |