Bug 1076872

Summary: [abrt] powerline: update_refs(): python2.7 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: John Schmitt <marmalodak>
Component: powerlineAssignee: Andreas Schneider <asn>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: asn
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9cbb06aac13e8032594f06a0dec1a45531f3ac34
Whiteboard: abrt_hash:861a76f64c4e5652d9c92796dd487dea17e53b70
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 19:30:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description John Schmitt 2014-03-16 02:09:10 UTC
Description of problem:
powerline maybe?

Version-Release number of selected component:
powerline-0.0.1-6.20140226git70a94e.fc20

Additional info:
reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        /usr/bin/python /bin/powerline tmux left
crash_function: update_refs
executable:     /usr/bin/python2.7
kernel:         3.13.6-200.fc20.x86_64
runlevel:       N 3
type:           CCpp
uid:            1000

Truncated backtrace:
warning: core file may not match specified executable file.
[New LWP 15286]
warning: File "/var/cache/abrt-di/usr/lib/debug/usr/lib64/libpython2.7.so.1.0.debug-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load:/usr/bin/mono-gdb.py".
To enable execution of this file add
	add-auto-load-safe-path /var/cache/abrt-di/usr/lib/debug/usr/lib64/libpython2.7.so.1.0.debug-gdb.py
line to your configuration file "/home/john/.gdbinit".
To completely disable this security protection add
	set auto-load safe-path /
line to your configuration file "/home/john/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
	info "(gdb)Auto-loading safe path"
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/python /bin/powerline tmux left'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  update_refs (containers=<optimized out>) at /usr/src/debug/Python-2.7.5/Modules/gcmodule.c:400
400	/usr/src/debug/Python-2.7.5/Modules/gcmodule.c: No such file or directory.

Thread 1 (Thread 0x7f147fca8740 (LWP 15286)):
#0  update_refs (containers=<optimized out>) at /usr/src/debug/Python-2.7.5/Modules/gcmodule.c:400
        gc = 0xd007f147fb2a5d0
#1  collect (generation=0) at /usr/src/debug/Python-2.7.5/Modules/gcmodule.c:998
        i = <optimized out>
        m = 0
        n = 0
        young = <optimized out>
        old = 0x7f147fa9f290 <generations+48>
        unreachable = {gc = {gc_next = 0xd0, gc_prev = 0x16c, gc_refs = 115}, dummy = <invalid float value>}
        finalizers = {gc = {gc_next = 0xf84530, gc_prev = 0x7f147f7850ca <_PyString_Eq+42>, gc_refs = 140737463596448}, dummy = <invalid float value>}

Comment 1 John Schmitt 2014-03-16 02:09:13 UTC
Created attachment 874948 [details]
File: backtrace

Comment 2 John Schmitt 2014-03-16 02:09:15 UTC
Created attachment 874949 [details]
File: cgroup

Comment 3 John Schmitt 2014-03-16 02:09:17 UTC
Created attachment 874950 [details]
File: core_backtrace

Comment 4 John Schmitt 2014-03-16 02:09:18 UTC
Created attachment 874951 [details]
File: dso_list

Comment 5 John Schmitt 2014-03-16 02:09:19 UTC
Created attachment 874952 [details]
File: environ

Comment 6 John Schmitt 2014-03-16 02:09:20 UTC
Created attachment 874953 [details]
File: exploitable

Comment 7 John Schmitt 2014-03-16 02:09:22 UTC
Created attachment 874954 [details]
File: limits

Comment 8 John Schmitt 2014-03-16 02:09:23 UTC
Created attachment 874955 [details]
File: maps

Comment 9 John Schmitt 2014-03-16 02:09:24 UTC
Created attachment 874956 [details]
File: open_fds

Comment 10 John Schmitt 2014-03-16 02:09:26 UTC
Created attachment 874957 [details]
File: proc_pid_status

Comment 11 John Schmitt 2014-03-16 02:09:27 UTC
Created attachment 874958 [details]
File: var_log_messages

Comment 12 Fedora End Of Life 2015-05-29 11:16:03 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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 this bug is closed as described in the policy above.

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 13 Fedora End Of Life 2015-06-29 19:30:15 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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