Bug 846484 - [abrt] gitg-0.2.5-3.fc17: __GI___libc_free: Process /usr/bin/gitg was killed by signal 11 (SIGSEGV)
[abrt] gitg-0.2.5-3.fc17: __GI___libc_free: Process /usr/bin/gitg was killed ...
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-08-07 18:04 EDT by Tim Zorn
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:41 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 (4.58 KB, text/plain)
2012-08-07 18:04 EDT, Tim Zorn
no flags Details
File: backtrace (41.13 KB, text/plain)
2012-08-07 18:04 EDT, Tim Zorn
no flags Details
File: maps (35.21 KB, text/plain)
2012-08-07 18:04 EDT, Tim Zorn
no flags Details
File: dso_list (7.03 KB, text/plain)
2012-08-07 18:04 EDT, Tim Zorn
no flags Details

  None (edit)
Description Tim Zorn 2012-08-07 18:04:49 EDT
libreport version: 2.0.10
abrt_version:   2.0.10
backtrace_rating: 4
cmdline:        gitg
comment:        I clicked commit (signoff was checked and there was a commit message)
crash_function: __GI___libc_free
executable:     /usr/bin/gitg
kernel:         3.4.6-2.fc17.x86_64
pid:            7085
pwd:            /home/systemdisc
remote_result:  795135
time:           Tue 07 Aug 2012 05:58:23 PM EDT
uid:            1000
username:       systemdisc

backtrace:      Text file, 42113 bytes
core_backtrace: Text file, 4687 bytes
dso_list:       Text file, 7202 bytes
maps:           Text file, 36057 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                 63156                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       63156                63156                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:	14862
:flags:	0102002
:pos:	14862
:flags:	0102002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004000
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02
:pos:	0
:flags:	02004002

:Aug  7 17:38:49 home yum[6842]: Installed: gitg-libs-0.2.5-3.fc17.x86_64
:Aug  7 17:38:50 home yum[6842]: Installed: gitg-0.2.5-3.fc17.x86_64
:Aug  7 17:58:23 home kernel: [ 1988.743876] gitg[7085]: segfault at 0 ip 000000380008017c sp 00007fff64b15db8 error 4 in libc-2.15.so[3800000000+1ac000]
:Aug  7 17:58:23 home abrt[14391]: Saved core dump of pid 7085 (/usr/bin/gitg) to /var/spool/abrt/ccpp-2012-08-07-17:58:23-7085 (54849536 bytes)
Comment 1 Tim Zorn 2012-08-07 18:04:52 EDT
Created attachment 602866 [details]
File: core_backtrace
Comment 2 Tim Zorn 2012-08-07 18:04:54 EDT
Created attachment 602867 [details]
File: backtrace
Comment 3 Tim Zorn 2012-08-07 18:04:57 EDT
Created attachment 602868 [details]
File: maps
Comment 4 Tim Zorn 2012-08-07 18:04:59 EDT
Created attachment 602869 [details]
File: dso_list
Comment 5 Fedora End Of Life 2013-07-03 18:46:02 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 6 Fedora End Of Life 2013-07-31 20:52:47 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.