Description of problem: From within ipython3 I performed help() followed by modules. Python3 crashed with a stack-trace originating from somewhere within libcomps: Program received signal SIGSEGV, Segmentation fault. 0x00007fffd46f1687 in PyInit__libpycomps () at /usr/src/debug/libcomps-e11ff1b16f901139ee4e9d6ccc9219982ceaebd5/py3/libcomps/src/python/src/pycomps.c:1038 1038 Py_INCREF(PyCOMPSExc_ParserError); I can reproduce it on my system anytime. Version-Release number of selected component: python3-ipython-console-2.4.1-8.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/python3 /bin/ipython3 crash_function: PyInit__libpycomps executable: /usr/bin/python3.4 global_pid: 9070 kernel: 4.1.7-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 0 (10 frames) #0 PyInit__libpycomps at /usr/src/debug/libcomps-e11ff1b16f901139ee4e9d6ccc9219982ceaebd5/py3/libcomps/src/python/src/pycomps.c:1038 #1 _PyImport_LoadDynamicModule at /usr/src/debug/Python-3.4.2/Python/importdl.c:88 #2 _imp_load_dynamic at /usr/src/debug/Python-3.4.2/Python/import.c:2263 #4 PyEval_EvalFrameEx at /usr/src/debug/Python-3.4.2/Python/ceval.c:4584 #6 PyEval_EvalCodeEx at /usr/src/debug/Python-3.4.2/Python/ceval.c:3614 #7 PyEval_EvalFrameEx at /usr/src/debug/Python-3.4.2/Python/ceval.c:4370 #10 PyEval_EvalCodeEx at /usr/src/debug/Python-3.4.2/Python/ceval.c:3614 #11 function_call at /usr/src/debug/Python-3.4.2/Objects/funcobject.c:632 #12 PyObject_Call at /usr/src/debug/Python-3.4.2/Objects/abstract.c:2067 #13 PyEval_EvalFrameEx at /usr/src/debug/Python-3.4.2/Python/ceval.c:4587
Created attachment 1079227 [details] File: backtrace
Created attachment 1079228 [details] File: cgroup
Created attachment 1079229 [details] File: core_backtrace
Created attachment 1079230 [details] File: dso_list
Created attachment 1079231 [details] File: environ
Created attachment 1079232 [details] File: limits
Created attachment 1079233 [details] File: maps
Created attachment 1079234 [details] File: mountinfo
Created attachment 1079235 [details] File: namespaces
Created attachment 1079236 [details] File: open_fds
Created attachment 1079237 [details] File: proc_pid_status
Created attachment 1079238 [details] File: var_log_messages
I can't reproduce this on my system. Do you get any useful information if you run ipython3 under valgrind?
I have reduced the problem to the simplest I currently can do: If I run python3 from within gdb I get the current backtrace (python3-backtrace.log) Also I tried the suggestion of running python3 with valgrind (--check-leaks=full) result is in python3-valgrind.log.
Created attachment 1085847 [details] python3-valgrind.log
Created attachment 1085848 [details] file: python3-backtrace.log
Created attachment 1085849 [details] file: python3-packages-installed.txt
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.