Bug 829563 - [abrt] gitg-0.2.5-3.fc17: _IO_file_doallocate: Process /usr/bin/gitg was killed by signal 11 (SIGSEGV)
[abrt] gitg-0.2.5-3.fc17: _IO_file_doallocate: Process /usr/bin/gitg was kill...
Product: Fedora
Classification: Fedora
Component: gitg (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Ignacio Casal Quinteiro (nacho)
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-06-06 23:21 EDT by prorok12
Modified: 2013-07-31 20:52 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-31 20:52:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: core_backtrace (136.09 KB, text/plain)
2012-06-06 23:21 EDT, prorok12
no flags Details
File: event_log (1.29 KB, text/plain)
2012-06-06 23:21 EDT, prorok12
no flags Details
File: backtrace (499.69 KB, text/plain)
2012-06-06 23:21 EDT, prorok12
no flags Details
File: smolt_data (6.59 KB, text/plain)
2012-06-06 23:21 EDT, prorok12
no flags Details
File: maps (28.63 KB, text/plain)
2012-06-06 23:21 EDT, prorok12
no flags Details
File: dso_list (6.82 KB, text/plain)
2012-06-06 23:21 EDT, prorok12
no flags Details

  None (edit)
Description prorok12 2012-06-06 23:21:00 EDT
libreport version: 2.0.10
abrt_version:   2.0.10
backtrace_rating: 4
cmdline:        gitg
crash_function: _IO_file_doallocate
executable:     /usr/bin/gitg
kernel:         3.3.7-1.fc17.x86_64
pid:            30772
pwd:            /home/prorok
time:           Чтв 07 Июн 2012 06:16:27
uid:            1000
username:       prorok

backtrace:      Text file, 511686 bytes
core_backtrace: Text file, 139357 bytes
dso_list:       Text file, 6987 bytes
event_log:      Binary file, 1325 bytes
maps:           Text file, 29318 bytes
smolt_data:     Binary file, 6744 bytes


:'LESSOPEN=||/usr/bin/lesspipe.sh %s'

:Limit                     Soft Limit           Hard Limit           Units     
:Max cpu time              unlimited            unlimited            seconds   
:Max file size             unlimited            unlimited            bytes     
:Max data size             unlimited            unlimited            bytes     
:Max stack size            8388608              unlimited            bytes     
:Max core file size        0                    unlimited            bytes     
:Max resident set          unlimited            unlimited            bytes     
:Max processes             1024                 47545                processes 
:Max open files            1024                 4096                 files     
:Max locked memory         65536                65536                bytes     
:Max address space         unlimited            unlimited            bytes     
:Max file locks            unlimited            unlimited            locks     
:Max pending signals       47545                47545                signals   
:Max msgqueue size         819200               819200               bytes     
:Max nice priority         0                    0                    
:Max realtime priority     0                    0                    
:Max realtime timeout      unlimited            unlimited            us        

:pos:	0
:flags:	0100000
:pos:	51272
:flags:	0102002
:pos:	51272
:flags:	0102002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	0100000

:Jun  7 06:15:52 prorok-pc yum[26060]: Installed: gitg-libs-0.2.5-3.fc17.x86_64
:Jun  7 06:16:09 prorok-pc yum[26060]: Installed: gitg-0.2.5-3.fc17.x86_64
:Jun  7 06:16:27 prorok-pc kernel: [  786.030933] gitg[30772]: segfault at 7fff871a5fe8 ip 0000003d5526b6da sp 00007fff871a5ff0 error 6 in libc-2.15.so[3d55200000+1ac000]
:Jun  7 06:16:27 prorok-pc abrt[30774]: Saved core dump of pid 30772 (/usr/bin/gitg) to /var/spool/abrt/ccpp-2012-06-07-06:16:27-30772 (15446016 bytes)
Comment 1 prorok12 2012-06-06 23:21:05 EDT
Created attachment 590052 [details]
File: core_backtrace
Comment 2 prorok12 2012-06-06 23:21:07 EDT
Created attachment 590053 [details]
File: event_log
Comment 3 prorok12 2012-06-06 23:21:13 EDT
Created attachment 590054 [details]
File: backtrace
Comment 4 prorok12 2012-06-06 23:21:15 EDT
Created attachment 590055 [details]
File: smolt_data
Comment 5 prorok12 2012-06-06 23:21:17 EDT
Created attachment 590056 [details]
File: maps
Comment 6 prorok12 2012-06-06 23:21:20 EDT
Created attachment 590057 [details]
File: dso_list
Comment 7 Fedora End Of Life 2013-07-03 18:45:58 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is 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  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.
Comment 8 Fedora End Of Life 2013-07-31 20:52:38 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.