Bug 891633

Summary: [abrt] python-2.7.3-13.fc18: PyEval_EvalFrameEx: Process /usr/bin/python2.7 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jan Teichmann <jan.teichmann>
Component: pythonAssignee: Dave Malcolm <dmalcolm>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: bkabrda, dmalcolm, ivazqueznet, jonathansteffan, tomspur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:8cc3714ce7abaa4f30b06d029b41165649316715
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-10 09:03:12 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: dso_list
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Jan Teichmann 2013-01-03 13:17:18 UTC 
Version-Release number of selected component:
python-2.7.3-13.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/python -u /usr/bin/abrt-action-install-debuginfo --size_mb=4096
core_backtrace: 
crash_function: PyEval_EvalFrameEx
environ:        PATH=/usr/bin:/bin
executable:     /usr/bin/python2.7
kernel:         3.6.10-4.fc18.x86_64
remote_result:  650561
uid:            173

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.3/Python/ceval.c:2147
 #1 fast_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4184
 #2 call_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4119
 #3 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.3/Python/ceval.c:2740
 #4 fast_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4184
 #5 call_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4119
 #6 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.3/Python/ceval.c:2740
 #7 fast_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4184
 #8 call_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4119
 #9 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.3/Python/ceval.c:2740
Comment 1 Jan Teichmann 2013-01-03 13:17:27 UTC 
Created attachment 672079 [details]
File: backtrace
Comment 2 Jan Teichmann 2013-01-03 13:17:29 UTC 
Created attachment 672080 [details]
File: cgroup
Comment 3 Jan Teichmann 2013-01-03 13:17:31 UTC 
Created attachment 672081 [details]
File: dso_list
Comment 4 Jan Teichmann 2013-01-03 13:17:35 UTC 
Created attachment 672082 [details]
File: limits
Comment 5 Jan Teichmann 2013-01-03 13:17:38 UTC 
Created attachment 672083 [details]
File: maps
Comment 6 Jan Teichmann 2013-01-03 13:17:39 UTC 
Created attachment 672084 [details]
File: open_fds
Comment 7 Jan Teichmann 2013-01-03 13:17:42 UTC 
Created attachment 672085 [details]
File: proc_pid_status
Comment 8 Jan Teichmann 2013-01-03 13:17:44 UTC 
Created attachment 672086 [details]
File: var_log_messages
Comment 9 Jan Teichmann 2013-01-10 09:03:12 UTC 
I noticed more strange memory corruption in other programs recently and as it turned out I had a defective RAM module. Effects were very random and rare but could be the cause of most memory corruption I lately reported. I assumed it is related to the beta state of F18 so I didnt suspect the RAM at first but MemTest found a small address range with errors.
I am extremely sorry for taking up your time hunting down bugs which are most likely not there. I decided to close my latest bug reports as I can not assure that the memory corruption was actually caused by the program rather than the defect RAM module.