After upgrade from Pycharm 2017.2.3 to Pycharm 2017.1.4 Pycharm's Debugger suggested to build cpython (or sth associated with it):
path/to/my/python /opt/pycharm-community-2017.1.4/helpers/pydev/setup_cython.py build_ext --inplace
After I did this, Debugger now instantly returns this error:
Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)
I found out that there was similar issue with cpython (https://youtrack.jetbrains.com/issue/PY-23273) but I cannot use the workaround mentioned there because I am missing the files it suggest to remove... I am not using cython, I wish I ignored this message about building it..
I am on linux (SMP Debian 3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux)
Python 2.7
I've fixed it by disabling PyQt compatible option in PyCharms's debugger settings (Build, Execution, Deployment > Python Debugger). I don't use PyQt, so I have not met any troubles
I did change Pycharm from 2017.1.4 to Pycharm EAP 2017.2, but with no effect.
I solved the problem by making new python virtual environment and changing default Pycharm interpreter to it. Not the fastest solution I guess, but at least it worked.
Pycharm now again gives suggestions of building something for Cython, but now I just ignore it.
I had the same issue with 2018.3 after updating and installing Cython for fast debugging.
The issue was with gevent library.
Solved enabling Gevent compatible option and disabling PyQt compatible.
I agree with James.
I meet the same question as you after I install PYQT. After I uninstall pyqt by Pycharm's "Preference->Project:your current project->Project Interpreter" find pyqt and push '-' button, the debug works.
What is interesting is that when I run a script which includes 'from PyQt4 import QtGui'. The pyqt package installed auto. And the debug does not work again. So I uninstall pyqt again and debug works one more time!
So I think there may be some package make debug not work , what you should do is just find and uninstall it. The crime package is often the pyqt, matplotlib or something similary.
i meet this problem, and i search for it a long time, all caused by the compatible of pyqt,So I think a good idea to solve it....
- uninstall pyqt and matplotlib
- Fist install pyqt
- Second install matplotlib
then the problem was solved happily.
Mine worked after I removed pyqt5 bindings.
sudo apt-get remove python3-pyqt5
This wasn't happening to me because of building cpython. It was because I had installed an unrelated program. Hope it helps.
I had the same with 2017.1.4 Problem was resolved after update to 2017.1.5
Try clearing all your breakpoints. Worked for me. Also check you have no problem when doing Run instead of Debug.
来源：https://stackoverflow.com/questions/45016449/pycharm-debugger-instantly-exits-with-139-code