Bug 726461
Summary: | [abrt] ipython-0.10.2-1.fc15: PyArray_API: Process /usr/bin/python was killed by signal 11 (SIGSEGV) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Germán Racca <gracca> | ||||||||
Component: | scipy | Assignee: | Jef Spaleta <jspaleta> | ||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 15 | CC: | bkearney, gwync, jspaleta, orion, shahms, tomspur | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | abrt_hash:7a24e3a8afe292ec311d3e2b5cf7a52ed12e95c8 | ||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2012-07-26 11:12: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
Germán Racca
2011-07-28 17:34:30 UTC
Created attachment 515771 [details]
File: dso_list
Created attachment 515772 [details]
File: maps
Created attachment 515773 [details]
File: backtrace
Thanks for filling this bug report. Looks like the crash happend in: /usr/lib64/python2.7/site-packages/scipy/fftpack/_fftpack.so You could try to uninstall scipy and see if that "solves" the modules command. I can't reproduce it with the steps from above with the release candidate 2 of the new ipython and the 0.10.1 version out of git repository: scipy-0.9.0-1.fc15.x86_64 (the same like you have in dso_list) Reassigning to scipy, maybe they can reproduce it/help track this down. Closing as a dub of the same bug against f16. *** This bug has been marked as a duplicate of bug 843416 *** |