Bug 891633 - [abrt] python-2.7.3-13.fc18: PyEval_EvalFrameEx: Process /usr/bin/python2.7 was killed by signal 11 (SIGSEGV)
Summary: [abrt] python-2.7.3-13.fc18: PyEval_EvalFrameEx: Process /usr/bin/python2.7 w...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: python
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dave Malcolm
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8cc3714ce7abaa4f30b06d029b4...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-03 13:17 UTC by Jan Teichmann
Modified: 2013-01-10 09:03 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-10 09:03:12 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (384.50 KB, text/plain)
2013-01-03 13:17 UTC, Jan Teichmann 		no flags Details
File: cgroup (126 bytes, text/plain)
2013-01-03 13:17 UTC, Jan Teichmann 		no flags Details
File: dso_list (9.89 KB, text/plain)
2013-01-03 13:17 UTC, Jan Teichmann 		no flags Details
File: limits (1.29 KB, text/plain)
2013-01-03 13:17 UTC, Jan Teichmann 		no flags Details
File: maps (46.81 KB, text/plain)
2013-01-03 13:17 UTC, Jan Teichmann 		no flags Details
File: open_fds (567 bytes, text/plain)
2013-01-03 13:17 UTC, Jan Teichmann 		no flags Details
File: proc_pid_status (924 bytes, text/plain)
2013-01-03 13:17 UTC, Jan Teichmann 		no flags Details
File: var_log_messages (657 bytes, text/plain)
2013-01-03 13:17 UTC, Jan Teichmann 		no flags Details
View All

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.
Note You need to log in before you can comment on or make changes to this bug.