Bug 1000766 - [abrt] yumex-3.0.10-1.fc18: tupledealloc: Process /usr/bin/python2.7 was killed by signal 11 (SIGSEGV)
[abrt] yumex-3.0.10-1.fc18: tupledealloc: Process /usr/bin/python2.7 was kill...
Status: CLOSED CANTFIX
Product: Fedora
Classification: Fedora
Component: yumex (Show other bugs)
18
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Tim Lauridsen
Fedora Extras Quality Assurance
abrt_hash:6f3ac0b58907a94cd83c61fcbab...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-24 21:11 EDT by das
Modified: 2013-09-10 08:31 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-09-10 08:31:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (42.45 KB, text/plain)
2013-08-24 21:11 EDT, das
no flags Details
File: cgroup (125 bytes, text/plain)
2013-08-24 21:11 EDT, das
no flags Details
File: core_backtrace (1.84 KB, text/plain)
2013-08-24 21:12 EDT, das
no flags Details
File: dso_list (10.71 KB, text/plain)
2013-08-24 21:12 EDT, das
no flags Details
File: environ (257 bytes, text/plain)
2013-08-24 21:12 EDT, das
no flags Details
File: limits (1.29 KB, text/plain)
2013-08-24 21:12 EDT, das
no flags Details
File: maps (52.29 KB, text/plain)
2013-08-24 21:12 EDT, das
no flags Details
File: open_fds (105 bytes, text/plain)
2013-08-24 21:12 EDT, das
no flags Details
File: proc_pid_status (912 bytes, text/plain)
2013-08-24 21:12 EDT, das
no flags Details
File: var_log_messages (332 bytes, text/plain)
2013-08-24 21:12 EDT, das
no flags Details

  None (edit)
Description das 2013-08-24 21:11:50 EDT
Version-Release number of selected component:
yumex-3.0.10-1.fc18

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/bin/python -E /usr/share/yumex/yum_childtask.py 2 True False /etc/yum.conf
crash_function: tupledealloc
executable:     /usr/bin/python2.7
kernel:         3.10.6-100.fc18.x86_64
runlevel:       N 5
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 tupledealloc at /usr/src/debug/Python-2.7.3/Objects/tupleobject.c:236
 #1 code_dealloc at /usr/src/debug/Python-2.7.3/Objects/codeobject.c:310
 #2 func_dealloc at /usr/src/debug/Python-2.7.3/Objects/funcobject.c:454
 #3 insertdict at /usr/src/debug/Python-2.7.3/Objects/dictobject.c:539
 #4 PyDict_SetItem at /usr/src/debug/Python-2.7.3/Objects/dictobject.c:784
 #5 _PyModule_Clear at /usr/src/debug/Python-2.7.3/Objects/moduleobject.c:138
 #6 PyImport_Cleanup at /usr/src/debug/Python-2.7.3/Python/import.c:498
 #7 Py_Finalize at /usr/src/debug/Python-2.7.3/Python/pythonrun.c:454
 #9 Py_Exit at /usr/src/debug/Python-2.7.3/Python/pythonrun.c:1768
 #10 handle_system_exit at /usr/src/debug/Python-2.7.3/Python/pythonrun.c:1142
Comment 1 das 2013-08-24 21:11:55 EDT
Created attachment 789987 [details]
File: backtrace
Comment 2 das 2013-08-24 21:11:59 EDT
Created attachment 789988 [details]
File: cgroup
Comment 3 das 2013-08-24 21:12:02 EDT
Created attachment 789989 [details]
File: core_backtrace
Comment 4 das 2013-08-24 21:12:06 EDT
Created attachment 789990 [details]
File: dso_list
Comment 5 das 2013-08-24 21:12:10 EDT
Created attachment 789991 [details]
File: environ
Comment 6 das 2013-08-24 21:12:13 EDT
Created attachment 789992 [details]
File: limits
Comment 7 das 2013-08-24 21:12:21 EDT
Created attachment 789993 [details]
File: maps
Comment 8 das 2013-08-24 21:12:25 EDT
Created attachment 789994 [details]
File: open_fds
Comment 9 das 2013-08-24 21:12:30 EDT
Created attachment 789995 [details]
File: proc_pid_status
Comment 10 das 2013-08-24 21:12:34 EDT
Created attachment 789996 [details]
File: var_log_messages
Comment 11 Tim Lauridsen 2013-09-10 08:31:25 EDT
Something deep inside python is blowing up, it cant do much about it.
if it happens every time, then you can open a bug report against python

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